Deletes a record from the database by its ID.
AI agents call delete_record to permanently remove resources in Pg Mnemosyne — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data from the database without the possibility of automatic recovery (unless backups exist outside this tool's scope). Deletion is an irreversible operation that cannot be undone through the tool itself. Given the server's role as a 'super memory, task tracker, and dynamic database manager,' deleting records could result in permanent loss of important task, session, or coordination data.
From the tool's definition Tool name is 'delete_record' and description states 'Deletes a record from the database by its ID.' The verb 'deletes' combined with database records indicates irreversible data removal.
Attacks that exploit this kind of access
Deletes a record from the database by its ID. It is categorised as a Destructive tool in the Pg Mnemosyne MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pg Mnemosyne MCP server in PolicyLayer and add a rule for delete_record: 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 Pg Mnemosyne. Nothing to install.
delete_record 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_record 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_record. 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_record is provided by the Pg Mnemosyne MCP server (janadasroor/pg-mnemosyne-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 →