DESTRUCTIVE: permanently delete a project AND every memory inside it. All memories labelled with this project name are removed along with their stored data. This is irreversible. Use ragionex_delete_memory (with explicit IDs) when only some memories should be removed. Returns the count of memorie...
AI agents call ragionex_delete_memory_project to permanently remove resources in Ragionex Memory MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes bulk data (entire project plus all contained memories). The description explicitly warns it is destructive and irreversible, meeting the Destructive category definition. While the blast radius depends on project size, deletion of all project memories cannot be undone, warranting high severity.
From the tool's definition Tool description explicitly states: 'DESTRUCTIVE: permanently delete a project AND every memory inside it. All memories labelled with this project name are removed along with their stored data. This is irreversible.'
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
DESTRUCTIVE: permanently delete a project AND every memory inside it. All memories labelled with this project name are removed along with their stored data. This is irreversible. Use ragionex_delete_memory (with explicit IDs) when only some memories should be removed. Returns the count of memories deleted. It is categorised as a Destructive tool in the Ragionex Memory MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ragionex Memory MCP server in PolicyLayer and add a rule for ragionex_delete_memory_project: 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 Ragionex Memory MCP. Nothing to install.
ragionex_delete_memory_project 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 ragionex_delete_memory_project 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 ragionex_delete_memory_project. 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.
ragionex_delete_memory_project is provided by the Ragionex Memory MCP server (ragionex/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ragionex_delete_memory_project is one line of Ragionex Memory's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →