create_issue_category · Redmine MCP: Risk & Policy

WHAT IT DOES

What create_issue_category does on Redmine

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

The tool creates a new issue category, which is a reversible operation that adds metadata/configuration to a project. This is a Write operation (creates data) rather than Read (no retrieval), Destructive (reversible), Execute (no external command execution), Financial (no monetary impact), or Other.

From the tool's definition Tool name 'create_issue_category' and description 'Create a new issue category for a project' indicate the tool creates/adds new data to a Redmine instance.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_issue_category Rate-limited

create_issue_category 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_category": {
      "limits": [
        {
          "counter": "create_issue_category_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_category

What does the create_issue_category tool do? +

Create a new issue category for a project. 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_category? +

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

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

Can I rate-limit create_issue_category? +

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

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

create_issue_category is provided by the Redmine MCP server (yenpu/redmine-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.