AI agents call getIssue to retrieve information from Backlog MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves data from the Backlog issue tracking system. The verb 'get' combined with the description clearly indicates a read-only operation that does not create, modify, delete, or execute any code. There is no risk of data modification or destructive actions. Blast radius is minimal as it only exposes existing issue data that the authenticated user is already authorized to view.
From the tool's definition The tool name 'getIssue' and Japanese description '特定のBacklog課題を取得します' (meaning 'retrieves/obtains a specific Backlog issue') indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access getIssue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Backlog MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getIssue:
{
"version": "1",
"default": "deny",
"tools": {
"getIssue": {}
}
}getIssue 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.
特定のBacklog課題を取得します. It is categorised as a Read tool in the Backlog MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Backlog MCP Server MCP server in PolicyLayer and add a rule for getIssue: 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 Backlog MCP Server. Nothing to install.
getIssue 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 getIssue 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 getIssue. 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.
getIssue is provided by the Backlog MCP Server MCP server (jootsuki/backlog-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Backlog 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.
4 Backlog MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.