get_issues

What get_issues does on Aos

AI agents call get_issues to retrieve information from Aos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameters from the server's own tool schema.

Why get_issues is rated Low

The 'get_' prefix strongly suggests data retrieval with no side effects. In the context of a task/issue tracking system (evidenced by sibling tools like create_issue, create_task, create_todo), 'get_issues' almost certainly queries or lists existing issues. No modification, deletion, or execution is implied. Confidence is moderate-high due to empty description, but the naming convention is reliable.

From the tool's definition Tool name 'get_issues' follows the Read pattern (get/retrieve). Description is empty, so classification relies on naming convention and the pattern of sibling tools (many create_* tools indicate a task/project management system).

The rule that runs get_issues safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_issues, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_issues": {}
  }
}

Questions about get_issues