AI agents use create_issue 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.
Creating an issue in a project management system modifies state by adding a new record, which is reversible (the issue can be updated or deleted later). This is a Write operation, not Execute or Destructive. Severity is medium because misuse could spam or pollute a project with unwanted issues, but the blast radius is limited to issue creation without financial or destructive consequences.
From the tool's definition Tool name is 'create_issue' with verb 'create' indicating data creation. Server description confirms the tool interacts with 'issues' in a Redmine system.
Attacks that exploit this kind of access
create_issue. 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.
Register the Redmine MCP server in PolicyLayer and add a rule for create_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. Nothing to install.
create_issue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_issue is provided by the Redmine MCP server (KalvadTech/redmine-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →