AI agents use redmine_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.
This tool creates new issues in Redmine, which modifies the system state by adding data. This is a reversible operation (issues can be deleted), so it falls under Write rather than Destructive. Severity is medium because bulk or malicious issue creation could degrade system usability and create noise, but does not directly destroy data or move money.
From the tool's definition Tool name is 'redmine_create_issue' and description states 'Create a new Redmine issue.' The action is creating (adding) new data to the Redmine system, which is a write operation.
Attacks that exploit this kind of access
[Stable] Create a new Redmine issue. Returns the created issue with its assigned ID. 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 redmine_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.
redmine_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 redmine_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 redmine_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.
redmine_create_issue 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.
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 →