AI agents call delete_team 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.
This tool permanently removes team configuration data, which cannot be undone. While not as critical as deleting user data or financial records, deleting an entire team configuration represents an irreversible destructive action with significant impact on the system's orchestration capabilities. Classified as Destructive (more severe than Write) due to the permanent, non-reversible nature of deletion.
From the tool's definition Tool name 'delete_team' combined with description stating it deletes/removes ('删除') a team's configuration. The verb 'delete' in the tool name and the Chinese character '删除' (meaning 'delete' or 'remove') in the description indicate irreversible data removal.
Documented attack patterns abuse exactly the kind of access delete_team gives an 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_team:
{
"version": "1",
"default": "deny",
"hide": [
"delete_team"
]
}delete_team disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
删除一个团队的配置。. 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.
Register the AI Cognitive Nexus MCP server in PolicyLayer and add a rule for delete_team: 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.
delete_team 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_team 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_team. 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_team 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.
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.