Delete a knowledge base article
AI agents call delete_solution_article to permanently remove resources in Freshservice MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on knowledge base content. While not directly impacting financial systems or customer data in transit, the loss of a solution article removes documented organizational knowledge and cannot be undone without backup restoration. This is strictly destructive in nature.
From the tool's definition delete_solution_article: Delete a knowledge base article. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a knowledge base article. It is categorised as a Destructive tool in the Freshservice MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Freshservice MCP Server MCP server in PolicyLayer and add a rule for delete_solution_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 Freshservice MCP Server. Nothing to install.
delete_solution_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_solution_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_solution_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_solution_article is provided by the Freshservice MCP Server MCP server (tannertm0/freshservice-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 →