List issues across all projects (global search). No project_id needed.
AI agents call list_all_issues to retrieve information from Git MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that queries and retrieves issue data across projects. It does not create, modify, delete, or execute any changes. The lack of project_id requirement simply means it operates at a broader scope, but the fundamental action is data retrieval. Blast radius is minimal—an AI agent misusing this would at worst access issues it shouldn't see, not modify or destroy data.
From the tool's definition Tool name 'list_all_issues' and description 'List issues across all projects (global search)' indicate a retrieval/query operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_all_issues gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Git MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_all_issues:
{
"version": "1",
"default": "deny",
"tools": {
"list_all_issues": {}
}
}list_all_issues is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List issues across all projects (global search). No project_id needed. It is categorised as a Read tool in the Git MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Git MCP Server MCP server in PolicyLayer and add a rule for list_all_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 Git MCP Server. Nothing to install.
list_all_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_all_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_all_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_all_issues is provided by the Git MCP Server MCP server (yumeminami/git_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Git MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
33 Git MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.