update_issue · Redmine MCP OAuth Server MCP: Risk & Policy

WHAT IT DOES

What update_issue does on Redmine MCP OAuth Server

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

WHY IT NEEDS A POLICY

Why update_issue needs a policy

This tool modifies existing issue records (status, assignee, priority, etc.) and adds comments via journal entries. These changes are reversible—issues can be updated again or reverted. While it affects project tracking data, it does not delete data (Destructive), execute code (Execute), or involve financial transactions (Financial).

From the tool's definition Tool name 'update_issue' and description 'Update a Redmine issue' with parameters for modifying issue fields and adding journal comments indicate reversible modification of data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_issue Rate-limited

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": {
    "update_issue": {
      "limits": [
        {
          "counter": "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 MCP OAuth Server, so you can run agents against it safely.

FAQ

Questions about update_issue

What does the update_issue tool do? +

Update a Redmine issue. updates is a dict of issue fields; notes is added as a journal comment. It is categorised as a Write tool in the Redmine MCP OAuth Server 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? +

Register the Redmine MCP OAuth Server MCP server in PolicyLayer and add a rule for 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 MCP OAuth Server. Nothing to install.

What risk level is update_issue? +

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

Can I rate-limit update_issue? +

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

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

update_issue is provided by the Redmine MCP OAuth Server MCP server (zh/redmine_mcp_py). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.