[DEPRECATED] Delete a project state field by key.
AI agents call memento_delete_project_state to permanently remove resources in Memento — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs irreversible deletion of project state data. Even though it is marked deprecated, it retains destructive capability. Deletion of state fields in a memory system cannot be undone and represents data loss. This is more severe than Write (reversible modifications) and qualifies as Destructive due to the permanent removal of information from the temporal graph storage.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a project state field by key.' The action irreversibly removes data from the persistent memory system.
Attacks that exploit this kind of access
[DEPRECATED] Delete a project state field by key. It is categorised as a Destructive tool in the Memento MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Memento MCP server in PolicyLayer and add a rule for memento_delete_project_state: 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 Memento. Nothing to install.
memento_delete_project_state 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 memento_delete_project_state 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 memento_delete_project_state. 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.
memento_delete_project_state is provided by the Memento MCP server (joyciakira/memento). 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 →