copy_issue · Redmine MCP OAuth Server MCP: Risk & Policy

WHAT IT DOES

What copy_issue does on Redmine MCP OAuth Server

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

Copying an issue creates new data (a duplicate issue) in Redmine. This is a Write operation because it modifies the system state by adding a new record, and the action is reversible (the copied issue can be deleted). It does not irreversibly destroy data (Destructive), execute arbitrary code (Execute), handle financial transactions (Financial), or merely read data (Read).

From the tool's definition Tool description: 'Copy a Redmine issue.' The action of copying creates a new issue record in Redmine, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

copy_issue Rate-limited

copy_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": {
    "copy_issue": {
      "limits": [
        {
          "counter": "copy_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 copy_issue

What does the copy_issue tool do? +

Copy a Redmine issue. 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 copy_issue? +

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

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

Can I rate-limit copy_issue? +

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

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

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