Delete a Redmine group. confirm must be true.
AI agents call delete_group 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 Redmine group, which cannot be undone. Deletion of groups affects user permissions and access controls across the system. This is categorized as Destructive rather than Write because the action is irreversible. Severity is high because accidental or malicious deletion of groups could compromise organizational access control and require administrative recovery.
From the tool's definition Tool name is 'delete_group' and description states 'Delete a Redmine group.' The verb 'Delete' and the irreversible nature of removing a group from Redmine clearly indicate a destructive operation.
Attacks that exploit this kind of access
Delete a Redmine group. 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_group: 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_group 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_group 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_group. 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_group 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 →