delete_knowledge_base_article
AI agents call delete_knowledge_base_article to permanently remove resources in RunWhen Platform MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Any delete operation irreversibly removes data and cannot be undone without external recovery mechanisms. Even without a detailed description, the explicit 'delete' verb in the function name places this in the Destructive category with high severity due to potential data loss in a knowledge management system. Confidence is slightly reduced (0.85 vs.
From the tool's definition Tool name is 'delete_knowledge_base_article' — the 'delete' prefix indicates irreversible removal of data.
Attacks that exploit this kind of access
delete_knowledge_base_article. It is categorised as a Destructive tool in the RunWhen Platform MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the RunWhen Platform MCP server in PolicyLayer and add a rule for delete_knowledge_base_article: 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 RunWhen Platform MCP. Nothing to install.
delete_knowledge_base_article 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_knowledge_base_article 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_knowledge_base_article. 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_knowledge_base_article is provided by the RunWhen Platform MCP server (runwhen-contrib/runwhen-platform-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →