List issues in the backlog with priority scores (read-only, no locking)
AI agents call list_backlog to retrieve information from MCP GitHub Issue Priority Server 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 GitHub issue data with priority scores. It performs no modifications, deletions, or side effects—it is a pure read operation. The explicit 'read-only' designation in the description confirms this classification. The low severity reflects minimal blast radius if misused by an AI agent, as it only exposes already-visible issue information.
From the tool's definition Tool description explicitly states 'read-only, no locking' and the name 'list_backlog' indicates a query operation that retrieves and displays issue data without modification.
Attacks that exploit this kind of access
List issues in the backlog with priority scores (read-only, no locking). It is categorised as a Read tool in the MCP GitHub Issue Priority Server MCP Server, which means it retrieves data without modifying state.
Register the MCP GitHub Issue Priority Server MCP server in PolicyLayer and add a rule for list_backlog: 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 MCP GitHub Issue Priority Server. Nothing to install.
list_backlog 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_backlog 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_backlog. 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_backlog is provided by the MCP GitHub Issue Priority Server MCP server (steiner385/mcp-git-issue-priority). 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 →