Delete a Knowledge Base article by ID.
AI agents call delete_kb_article to permanently remove resources in InvGate Service Desk — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes knowledge base content without the ability to undo the operation. While the blast radius is limited to knowledge base articles (not financial systems or incident data), deletion is irreversible and could impact organizational knowledge and documentation.
From the tool's definition Tool name is 'delete_kb_article' and description states 'Delete a Knowledge Base article by ID.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a Knowledge Base article by ID. It is categorised as a Destructive tool in the InvGate Service Desk MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the InvGate Service Desk MCP server in PolicyLayer and add a rule for delete_kb_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 InvGate Service Desk. Nothing to install.
delete_kb_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_kb_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_kb_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_kb_article is provided by the InvGate Service Desk MCP server (oci:ghcr.io/tracegazer/invgate-service-desk-mcp:0.2.0). 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 →