redmine_update_issue · Redmine MCP: Risk & Policy

WHAT IT DOES

What redmine_update_issue does on Redmine

AI agents use redmine_update_issue 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 redmine_update_issue needs a policy

This tool creates or modifies data reversibly—a core Write operation. It updates issue records in Redmine without removing them, making it reversible and less severe than Execute or Destructive actions. Severity is medium because erroneous updates could corrupt issue data, affect multiple users' workflows, or require manual remediation, but changes are not permanent data loss.

From the tool's definition Tool name 'redmine_update_issue' and description 'Update an existing Redmine issue' indicate modification of data. The phrase 'Only provided fields are changed' confirms reversible updates without deletion or destruction.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

redmine_update_issue Rate-limited

redmine_update_issue 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": {
    "redmine_update_issue": {
      "limits": [
        {
          "counter": "redmine_update_issue_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 redmine_update_issue

What does the redmine_update_issue tool do? +

[Stable] Update an existing Redmine issue. Only provided fields are changed. Use. 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 redmine_update_issue? +

Register the Redmine MCP server in PolicyLayer and add a rule for redmine_update_issue: 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 redmine_update_issue? +

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

Can I rate-limit redmine_update_issue? +

Yes. Add a rate_limit block to the redmine_update_issue 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 redmine_update_issue completely? +

Set action: deny in the PolicyLayer policy for redmine_update_issue. 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 redmine_update_issue? +

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