Delete a memo by its ID.
AI agents call delete_memo to permanently remove resources in Memos MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (a memo) and cannot be undone. Although the blast radius is constrained to individual user memos rather than system-wide data, a misdirected or malicious call could permanently lose user content. Destructive is more severe than Write (which is reversible), so it takes precedence.
From the tool's definition Tool name: 'delete_memo'. Description: 'Delete a memo by its ID.' The verb 'delete' and the irreversible nature of removing a memo from the system matches the Destructive category definition.
Attacks that exploit this kind of access
Delete a memo by its ID. It is categorised as a Destructive tool in the Memos MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Memos MCP Server MCP server in PolicyLayer and add a rule for delete_memo: 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 Memos MCP Server. Nothing to install.
delete_memo 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_memo 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_memo. 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_memo is provided by the Memos MCP Server MCP server (shaorou459/memos-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 →