Delete an entity with guardrails; non-forced deletion requires prior archiving and no critical dependents.
AI agents call delete_entity to permanently remove resources in SQLite Project Memory MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Destructive category applies because the tool permanently deletes entities from the authoritative source of truth database. Even with safety measures in place (archiving requirement, dependent checks), the action itself is irreversible and removes data that cannot be recovered. The 'non-forced deletion' qualifier indicates a forced variant may exist that bypasses safeguards, increasing risk.
From the tool's definition Tool name is 'delete_entity' and description states it 'Delete[s] an entity'; this irreversibly removes data from the SQLite database.
Attacks that exploit this kind of access
Delete an entity with guardrails; non-forced deletion requires prior archiving and no critical dependents. It is categorised as a Destructive tool in the SQLite Project Memory MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SQLite Project Memory 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 SQLite Project Memory MCP. 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 SQLite Project Memory MCP server (webrtcgame/sqlite-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 →