redmine_update_issue · Redmine MCP server for Cursor MCP

WHAT IT DOES

What redmine_update_issue does on Redmine MCP server for Cursor

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

WHY IT NEEDS A POLICY

Why redmine_update_issue needs a policy

This tool creates or modifies data in a reversible manner (typical Write category). It updates issue records in Redmine, which can be undone by subsequent updates. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or perform irreversible operations.

From the tool's definition Tool name 'redmine_update_issue' and description 'Update an issue by ID' explicitly indicates modification of existing data. The phrase 'Only provided fields are sent' confirms it modifies specified fields reversibly.

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 MCP server for Cursor, so you can run agents against it safely.

FAQ

Questions about redmine_update_issue

What does the redmine_update_issue tool do? +

Update an issue by ID. Only provided fields are sent. Use extra_fields_json for custom_fields. It is categorised as a Write tool in the Redmine MCP server for Cursor 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 for Cursor 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 MCP server for Cursor. 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 for Cursor MCP server (mrajibh/redmine-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.