Critical Risk →

delete_agent

删除一个角色(Agent)。警告:这可能导致依赖此角色的团队失效。

How to control delete_agent ↓

What delete_agent does on AI Cognitive Nexus

AI agents call delete_agent to permanently remove resources in AI Cognitive Nexus — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_agent needs a policy

Deletion of agents is an irreversible operation that destroys data and can cause cascading failures in dependent teams. This matches the Destructive category (deletes data that cannot be undone). Severity is high because deleting an agent breaks team configurations and workflows, though it may not affect external systems or have financial impact.

From the tool's definition Tool name 'delete_agent' combined with description stating it deletes an agent (角色). The warning explicitly notes that dependent teams may become invalid, indicating irreversible state change and cascade effects.

Documented attack patterns abuse exactly the kind of access delete_agent gives an agent:

How to control delete_agent

PolicyLayer is an MCP gateway — it sits between your AI agents and AI Cognitive Nexus, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_agent:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_agent"
  ]
}

delete_agent disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register AI Cognitive Nexus — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_agent

What does the delete_agent tool do? +

删除一个角色(Agent)。警告:这可能导致依赖此角色的团队失效。. It is categorised as a Destructive tool in the AI Cognitive Nexus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_agent? +

Register the AI Cognitive Nexus MCP server in PolicyLayer and add a rule for delete_agent: 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 AI Cognitive Nexus. Nothing to install.

What risk level is delete_agent? +

delete_agent is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_agent? +

Yes. Add a rate_limit block to the delete_agent 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.

How do I block delete_agent completely? +

Set action: deny in the PolicyLayer policy for delete_agent. 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.

What MCP server provides delete_agent? +

delete_agent is provided by the AI Cognitive Nexus MCP server (simonutd/ai-cognitive-nexus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AI Cognitive Nexus tool call.

Start from AI Cognitive Nexus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

22 AI Cognitive Nexus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.