Delete a coordinator
AI agents call delete_coordinator to permanently remove resources in Red Team MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on a coordinator resource. Once deleted, the coordinator cannot be recovered without restoration from backups. While not directly involving user data or financial systems, deletion of a coordinator in a multi-agent orchestration platform could disrupt ongoing workflows, task coordination, and team configurations.
From the tool's definition delete_coordinator: Delete a coordinator. The tool name explicitly contains 'delete' and the description confirms it irreversibly removes a coordinator resource.
Attacks that exploit this kind of access
Delete a coordinator. It is categorised as a Destructive tool in the Red Team MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Red Team MCP server in PolicyLayer and add a rule for delete_coordinator: 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 Red Team MCP. Nothing to install.
delete_coordinator 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_coordinator 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_coordinator. 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_coordinator is provided by the Red Team MCP server (redteammcp/redteam-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 →