List issues in a project, optionally filtered by status and severity.
AI agents call list_issues to retrieve information from OverlayQA MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing issues from a project with optional filtering parameters. It performs a read-only operation returning data about issues without creating, modifying, deleting, or executing any code. The absence of any action verbs like create, update, delete, or execute, combined with the explicit 'List' action, clearly places this in the Read category.
From the tool's definition Tool name 'list_issues' and description 'List issues in a project, optionally filtered by status and severity' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List issues in a project, optionally filtered by status and severity. It is categorised as a Read tool in the OverlayQA MCP MCP Server, which means it retrieves data without modifying state.
Register the OverlayQA MCP server in PolicyLayer and add a rule for list_issues: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches OverlayQA MCP. Nothing to install.
list_issues is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_issues rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for list_issues. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
list_issues is provided by the OverlayQA MCP server (overlayqa/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →