update_issue_status · Redmine MCP: Risk & Policy

WHAT IT DOES

What update_issue_status does on Redmine

AI agents use update_issue_status to create or update resources in Redmine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Redmine environment.

WHY IT NEEDS A POLICY

Why update_issue_status needs a policy

Updating an issue's status modifies data reversibly within Redmine—it is a Write operation rather than Destructive (status changes are not permanent deletion) or Execute (not arbitrary code execution). Medium severity reflects the potential for workflow disruption if an AI agent sets incorrect statuses, but changes are reversible.

From the tool's definition Tool name 'update_issue_status' indicates modification of issue state. Server context shows task management and status updates as core functions. Description is empty, reducing confidence slightly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_issue_status Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_issue_status": {
      "limits": [
        {
          "counter": "update_issue_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Redmine, so you can run agents against it safely.

FAQ

Questions about update_issue_status

What does the update_issue_status tool do? +

update_issue_status. It is categorised as a Write tool in the Redmine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_issue_status? +

Register the Redmine 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. Nothing to install.

What risk level is update_issue_status? +

update_issue_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_issue_status? +

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.

How do I block update_issue_status completely? +

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.

What MCP server provides update_issue_status? +

update_issue_status is provided by the Redmine MCP server (xukaaaa/redmine-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.