Delete indexed custom content from AskX in Slite (deprecated)
AI agents call delete_custom_content to permanently remove resources in Slite MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes custom content from the Slite knowledge base's indexing system. Deletion is an irreversible operation that cannot be undone through normal means. Even though the tool is marked deprecated, it retains destructive capability. The high severity reflects the potential for unintended removal of important organizational knowledge.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete indexed custom content from AskX in Slite'. The verb 'delete' combined with the scope of removing indexed content indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete indexed custom content from AskX in Slite (deprecated). It is categorised as a Destructive tool in the Slite MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Slite MCP Server MCP server in PolicyLayer and add a rule for delete_custom_content: 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 Slite MCP Server. Nothing to install.
delete_custom_content 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_custom_content 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_custom_content. 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_custom_content is provided by the Slite MCP Server MCP server (takeokunn/slite-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 →