AI agents use updateIssue to create or update resources in Backlog MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Backlog MCP Server environment.
This tool creates or modifies data reversibly by updating issue records in Backlog. It does not delete data (not Destructive), execute arbitrary code (not Execute), or involve financial transactions (not Financial). The medium severity reflects that misuse could corrupt or alter important project tracking data, but changes are typically reversible through subsequent updates.
From the tool's definition Tool name 'updateIssue' and description 'Backlog課題を更新します' (updates Backlog issues) indicate modification of existing data. The description explicitly uses '更新' (update), which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access updateIssue 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 updateIssue:
{
"version": "1",
"default": "deny",
"tools": {
"updateIssue": {
"limits": [
{
"counter": "updateissue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}updateIssue stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Backlog課題を更新します. It is categorised as a Write tool in the Backlog MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Backlog MCP Server MCP server in PolicyLayer and add a rule for updateIssue: 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.
updateIssue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the updateIssue 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 updateIssue. 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.
updateIssue 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.