Critical Risk →

delete_knowledge

Delete knowledge

How to control delete_knowledge ↓

What delete_knowledge does on WeKnora MCP Server

AI agents call delete_knowledge to permanently remove resources in WeKnora MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_knowledge needs a policy

This tool permanently removes knowledge entries from the WeKnora knowledge management system. Deletion is an irreversible operation that destroys data without the ability to undo it. Even though the scope is limited to individual knowledge items (not the entire knowledge base), the destructive nature of permanent data loss makes this a high-severity risk.

From the tool's definition Tool name is 'delete_knowledge' with description 'Delete knowledge'. The verb 'delete' indicates irreversible removal of data.

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

How to control delete_knowledge

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

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

delete_knowledge 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 WeKnora MCP Server — 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_knowledge

What does the delete_knowledge tool do? +

Delete knowledge. It is categorised as a Destructive tool in the WeKnora MCP Server 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_knowledge? +

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

What risk level is delete_knowledge? +

delete_knowledge 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_knowledge? +

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

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

delete_knowledge is provided by the WeKnora MCP Server MCP server (nannaolympicbroadcast/weknoramcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every WeKnora MCP Server tool call.

Start from WeKnora MCP Server, 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.

21 WeKnora MCP Server 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.