AI agents use update_issue_status to create or update resources in Redmine MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Redmine MCP Server environment.
Updating an issue status modifies data but is reversible—status can be changed again to a previous state, and Redmine typically preserves version history. This is a Write operation rather than Destructive (which would be deletion) or Execute (which would be arbitrary script execution).
From the tool's definition Tool name 'update_issue_status' and description 'Update issue status' indicate modification of an existing issue's status field.
Documented attack patterns abuse exactly the kind of access update_issue_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Redmine MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_issue_status:
{
"version": "1",
"default": "deny",
"tools": {
"update_issue_status": {
"limits": [
{
"counter": "update_issue_status_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_issue_status 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.
Update issue status. It is categorised as a Write tool in the Redmine MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Redmine MCP Server MCP server in PolicyLayer and add a rule for update_issue_status: 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 Redmine MCP Server. Nothing to install.
update_issue_status 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 update_issue_status 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 update_issue_status. 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.
update_issue_status is provided by the Redmine MCP Server MCP server (snowild/redmine-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Redmine 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.
35 Redmine MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.