create_issue_relation · Redmine MCP: Risk & Policy

WHAT IT DOES

What create_issue_relation does on Redmine

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

This tool creates or establishes new relationships between issues, which is reversible (relations can be deleted via delete_issue_relation). It modifies the state of the Redmine system by adding metadata/connections but does not delete, execute code, move money, or destroy data. Write is the appropriate category.

From the tool's definition Tool description explicitly states 'Create a relation between two Redmine issues' with specific relation types (relates, duplicates, blocks, etc.). The action creates new data linking existing issues.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_issue_relation Rate-limited

create_issue_relation 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": {
    "create_issue_relation": {
      "limits": [
        {
          "counter": "create_issue_relation_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 create_issue_relation

What does the create_issue_relation tool do? +

[Alpha] Create a relation between two Redmine issues. Supported types: relates, duplicates, duplicated, blocks, blocked, precedes, follows, copied_to, copied_from. 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 create_issue_relation? +

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

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

Can I rate-limit create_issue_relation? +

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

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

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