ee_unlink

Remove symlinks for EE modules from addons path.

SERVEROdoo Claude MCP SOURCErosenvladimirov/odoo-claude-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/ee-unlink.md

WHAT IT DOES

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.

RISK

Why ee_unlink is rated Critical

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ee_unlink safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Odoo Claude MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ee_unlink, this is the rule to start with:

ee_unlink Hidden

ee_unlink is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every ee_unlink call is checked against it from then on.

FAQ

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.

KEEP EXPLORING

More on Odoo Claude, and thousands of servers like it.

This server

All 246 Odoo Claude tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →