AI agents call delete_chunk 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.
Deleting a chunk is a destructive action that cannot be undone—it permanently removes a unit of knowledge from the knowledge base. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone (delete, drop, purge, force-push).' The severity is high because unintended deletion of knowledge base chunks could corrupt or degrade the system's knowledge…
From the tool's definition Tool name 'delete_chunk' combined with description 'Delete a chunk' explicitly performs an irreversible deletion operation on data stored in the knowledge management system.
Documented attack patterns abuse exactly the kind of access delete_chunk gives an agent:
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_chunk:
{
"version": "1",
"default": "deny",
"hide": [
"delete_chunk"
]
}delete_chunk 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.
Delete a chunk. 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.
Register the WeKnora MCP Server MCP server in PolicyLayer and add a rule for delete_chunk: 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.
delete_chunk 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_chunk 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_chunk. 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_chunk 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.
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.