Critical Risk →

memory_delete

Delete a memory file from personal or shared storage.

How to control memory_delete ↓

What memory_delete does on Odoo Claude MCP

AI agents call memory_delete to permanently remove resources in Odoo Claude MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why memory_delete needs a policy

This tool irreversibly removes data (memory files) from storage and cannot be undone. Deletion operations that cannot be reversed fall under the Destructive category. Severity is high because an AI agent could maliciously or mistakenly delete important personal or shared data, with potential impact on multiple users (shared storage).

From the tool's definition Tool name 'memory_delete' combined with description 'Delete a memory file from personal or shared storage' explicitly performs irreversible deletion of data.

Documented attack patterns abuse exactly the kind of access memory_delete gives an agent:

How to control memory_delete

PolicyLayer is an MCP gateway — it sits between your AI agents and Odoo Claude MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "memory_delete"
  ]
}

memory_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Odoo Claude MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about memory_delete

What does the memory_delete tool do? +

Delete a memory file from personal or shared storage. It is categorised as a Destructive tool in the Odoo Claude MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on memory_delete? +

Register the Odoo Claude MCP server in PolicyLayer and add a rule for memory_delete: 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 Odoo Claude MCP. Nothing to install.

What risk level is memory_delete? +

memory_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit memory_delete? +

Yes. Add a rate_limit block to the memory_delete 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.

How do I block memory_delete completely? +

Set action: deny in the PolicyLayer policy for memory_delete. 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.

What MCP server provides memory_delete? +

memory_delete is provided by the Odoo Claude MCP server (rosenvladimirov/odoo-claude-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Odoo Claude MCP tool call.

Start from Odoo Claude MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

180 Odoo Claude MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.