knowledge_delete
A destructive tool on the Postking MCP server.
This record as markdown: /tools/io-github-bitsandtea-postking-mcp/knowledge-delete.md
What knowledge_delete does on Postking Mcp
AI agents call knowledge_delete to permanently remove resources in Postking Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why knowledge_delete is rated Critical
The 'delete' operation in a content management context typically removes data that cannot be recovered. This is categorized as Destructive rather than Write because deletion is irreversible. Severity is high because accidental or malicious deletion of knowledge/brand assets could cause significant operational harm, though without full documentation, a critical rating is not assigned.
From the tool's definition Tool name 'knowledge_delete' explicitly indicates deletion. While the description is empty, the verb 'delete' signals irreversible data removal.
Attacks that exploit this kind of access
The rule that runs knowledge_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postking Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For knowledge_delete, this is the rule to start with:
knowledge_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Postking Mcp, apply this rule, and every knowledge_delete call is checked against it from then on.
Questions about knowledge_delete
knowledge_delete is a destructive tool on the Postking MCP server. It is categorised as a Destructive tool in the Postking Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Postking MCP server in PolicyLayer and add a rule for knowledge_delete: 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 Postking Mcp. Nothing to install.
knowledge_delete 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 knowledge_delete 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 knowledge_delete. 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.
knowledge_delete is provided by the Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postking, and thousands of servers like it.
Across the catalogue