move_issue · Redmine MCP OAuth Server MCP: Risk & Policy

WHAT IT DOES

What move_issue does on Redmine MCP OAuth Server

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

Moving an issue between projects is a reversible write operation that modifies metadata and associations but does not delete data or execute arbitrary code. While it affects issue organization and permissions, it remains recoverable (the issue can be moved back).

From the tool's definition The tool "move_issue" modifies issue state by relocating it across projects. The Redmine API endpoint description indicates this changes the issue's project association, which is a reversible structural modification of data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_issue Rate-limited

move_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": {
    "move_issue": {
      "limits": [
        {
          "counter": "move_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 move_issue

What does the move_issue tool do? +

Move a Redmine issue to another project. 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 move_issue? +

Register the Redmine MCP OAuth Server MCP server in PolicyLayer and add a rule for move_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 move_issue? +

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

Can I rate-limit move_issue? +

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

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

move_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.