Delete an issue relation.
AI agents call delete_relation to permanently remove resources in Redmine — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes issue relations (dependencies, blocks, relates_to relationships between issues), which cannot be automatically recovered. While the blast radius is constrained to relation metadata rather than entire issues, the permanent deletion of structured data makes this Destructive rather than Write.
From the tool's definition Tool name explicitly uses 'delete' and description states 'Delete an issue relation' - an irreversible removal of data linking two issues.
Attacks that exploit this kind of access
Delete an issue relation. It is categorised as a Destructive tool in the Redmine MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Redmine MCP server in PolicyLayer and add a rule for delete_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.
delete_relation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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.
Set action: deny in the PolicyLayer policy for delete_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.
delete_relation 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 →