Critical Risk →

prune

Clear all data and reset knowledge graph

Risk signalsDestroys entire knowledge graph

Part of the Cognee server.

prune can permanently delete data in Cognee, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE COGNEE →

Free to start. No card required.

AI agents may call prune to permanently remove or destroy resources in Cognee. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call prune in a loop, permanently destroying resources in Cognee. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

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

See the full Cognee policy for all 7 tools.

Get this rule live on your own Cognee server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY COGNEE →

These attack patterns abuse exactly the kind of access prune gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so prune only ever does what you allow.

SECURE COGNEE →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the prune tool do? +

Clear all data and reset knowledge graph. It is categorised as a Destructive tool in the Cognee 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 prune? +

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

What risk level is prune? +

prune 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 prune? +

Yes. Add a rate_limit block to the prune 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 prune completely? +

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

prune is provided by the Cognee MCP server (@topoteretes/cognee). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Cognee tool call.

Deterministic rules across all 7 Cognee tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.