Delete an entity and all its associated data (observations and relations)
AI agents call delete_entity to permanently remove resources in MCP Memory LibSQL — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently deletes entities and cascades the deletion to associated observations and relations. This is a destructive operation that cannot be reversed, making it the most severe category applicable. Severity is 'high' rather than 'critical' because impact is scoped to the memory system's knowledge graph rather than affecting external systems, financial transactions, or system-wide integrity.
From the tool's definition Tool name is 'delete_entity' and description states 'Delete an entity and all its associated data (observations and relations)' — this irreversibly removes data and cannot be undone.
Documented attack patterns abuse exactly the kind of access delete_entity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Memory LibSQL, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_entity:
{
"version": "1",
"default": "deny",
"hide": [
"delete_entity"
]
}delete_entity disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an entity and all its associated data (observations and relations). It is categorised as a Destructive tool in the MCP Memory LibSQL MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Memory LibSQL MCP server in PolicyLayer and add a rule for delete_entity: 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 MCP Memory LibSQL. Nothing to install.
delete_entity 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_entity 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_entity. 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_entity is provided by the MCP Memory LibSQL MCP server (joleyline/mcp-memory-libsql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Memory LibSQL, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 MCP Memory LibSQL tools catalogued and risk-classified — across an index of 43,000+ MCP servers.