When listing Aikido feed issues:
- Use aikido-mcp:aikido_issues_list
- Call it when the user wants to list, show, count, or summarize Aikido feed issues.
- Pass scope fields only when the user (or workspace context) supplies them:
cloud_name,repo_name,repo_branch_name,vm_name,domain_name,container_name,team_name,workspace_name. - Optional
issue_types(array):open_source,leaked_secret,cloud,sast,iac,surface_monitoring,malware,eol,mobile,docker_container,cloud_instance,scm_security,license,ai_pentest— e.g. includeleaked_secretfor secrets. Omit when no category filter is needed. - SLA filters (booleans): set
out_of_sla: truewhen the user wants issues that are past their SLA, orsla_due_soon: truefor issues approaching their SLA deadline. - Pagination: use numeric
pageonly when the user needs more than the first page of results (zero-indexed). Only 25 findings are reported per page. Report to the user if there are more findings on following pages. - Detail lookup: pass
issue_id(string) to fetch one issue with more detail than the list returns. Use it when the user asks to dig into, explain, triage or fix a specific issue, or names an issue by its ID.issue_idoverrides every other filter — the call returns that single issue, so do not combine it with scope, type, SLA or pagination fields. - Present each issue exactly in this form (increment
#): Add extra bullets when the field is relevant, e.g.File: <issue_file> (line <issue_start_line>),Location: <location.type> <location.name> (<location.branch_name>),Issue link: <issue_link>,SLA due date: <issue_remediate_by_date>. - For an
issue_idlookup, keep the same format and then summarize the extra fields the detailed response carries.
If the Aikido MCP server is not available or fails, inform the user:
The Aikido MCP server is required for Aikido feed issues but is not available. Install it following the setup guide at reference.md, or run
/aikido:setup, then retry.


