Delete a relationship by id and record the removal in project history.
AI agents call delete_relationship 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.
This tool permanently removes relationship data from the SQLite database. While the scope is narrower than deleting entire entities (hence 'high' rather than 'critical'), the action is irreversible and destructive. An AI agent could misuse this to sever important project relationships, breaking graph integrity and losing historical context.
From the tool's definition Tool name: 'delete_relationship'; description explicitly states 'Delete a relationship by id'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a relationship by id and record the removal in project history. 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_relationship: 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_relationship 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_relationship 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_relationship. 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_relationship 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 →