Critical Risk →

ee_unlink

Remove symlinks for EE modules from addons path.

How to control ee_unlink ↓

What ee_unlink does on Odoo Claude MCP

AI agents call ee_unlink 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 ee_unlink needs a policy

This tool performs an irreversible deletion operation on symlinks pointing to Enterprise Edition modules. While the impact is scoped to symlink artifacts rather than data records, the operation cannot be undone and directly affects the system's module structure. In an Odoo multi-tenant environment with 197+ tools, misconfiguration of module paths could break application functionality.

From the tool's definition Tool name contains 'unlink' and description explicitly states 'Remove symlinks'. The verb 'remove' combined with 'unlink' (which in Unix/Linux systems means permanently delete file/symlink entries) indicates irreversible deletion of filesystem artifacts.

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

How to control ee_unlink

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 ee_unlink:

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

ee_unlink 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 ee_unlink

What does the ee_unlink tool do? +

Remove symlinks for EE modules from addons path. 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 ee_unlink? +

Register the Odoo Claude MCP server in PolicyLayer and add a rule for ee_unlink: 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 ee_unlink? +

ee_unlink 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 ee_unlink? +

Yes. Add a rate_limit block to the ee_unlink 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 ee_unlink completely? +

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

ee_unlink 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.