Delete a Redmine version. confirm must be true.
AI agents call delete_version to permanently remove resources in Redmine MCP OAuth Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a version from a Redmine project. Deletion is an irreversible operation with no undo capability. While not as severe as deleting an entire project (the blast radius is scoped to a single version), the action cannot be undone and affects project management artifacts. The explicit confirmation requirement ('confirm must be true') acknowledges the destructive nature.
From the tool's definition Tool name is 'delete_version' and description states 'Delete a Redmine version' — the verb 'delete' combined with the requirement to confirm indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a Redmine version. confirm must be true. It is categorised as a Destructive tool in the Redmine MCP OAuth Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Redmine MCP OAuth Server MCP server in PolicyLayer and add a rule for delete_version: 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 MCP OAuth Server. Nothing to install.
delete_version 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_version 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_version. 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_version is provided by the Redmine MCP OAuth Server MCP server (zh/redmine_mcp_py). 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 →