AI agents call list_my_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 only reads and retrieves issue data assigned to the user. It performs no mutations, deletions, executions, or financial operations. The blast radius of misuse is minimal—an agent could retrieve unwanted visibility into issues but cannot create, modify, or delete anything.
From the tool's definition Tool name 'list_my_issues' and description 'List issues assigned to me across all projects' indicate a query operation that retrieves data without modification or side effects.
Documented attack patterns abuse exactly the kind of access list_my_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_my_issues:
{
"version": "1",
"default": "deny",
"tools": {
"list_my_issues": {}
}
}list_my_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 assigned to me across all projects. 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_my_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_my_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_my_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_my_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_my_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.