Delete a specific document from the knowledge base.
AI agents call delete_document to permanently remove resources in MyAIGist MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool removes data that cannot be recovered—documents stored in the persistent local vector store are permanently deleted. This is a destructive operation with no undo capability. Severity is high because deletion of knowledge base contents could impair the system's functionality and eliminate information irreversibly, though the blast radius is limited to the local knowledge base rather than external systems.
From the tool's definition Tool name 'delete_document' combined with description 'Delete a specific document from the knowledge base' explicitly indicates irreversible removal of data from persistent storage.
Attacks that exploit this kind of access
Delete a specific document from the knowledge base. It is categorised as a Destructive tool in the MyAIGist MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MyAIGist MCP server in PolicyLayer and add a rule for delete_document: 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 MyAIGist MCP. Nothing to install.
delete_document 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_document 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_document. 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_document is provided by the MyAIGist MCP server (schwim23/myaigist_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 →