This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/odoo-unlink.md
What odoo_unlink does on Odoo Claude MCP
AI agents call odoo_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.
Why odoo_unlink is rated Critical
This tool irreversibly removes data from the Odoo database. An AI agent given IDs without proper safeguards could delete business-critical records (invoices, customers, transactions, configurations) with no undo. The blast radius is severe in a multi-tenant system managing financial and operational data across Bulgaria-localized entities. Highest severity warranted.
From the tool's definition Tool name 'odoo_unlink' and description 'Delete records by IDs.' — 'unlink' is Odoo's API method for permanent deletion; 'delete' is explicitly destructive.
Attacks that exploit this kind of access
The rule that runs odoo_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 odoo_unlink, this is the rule to start with:
odoo_unlink is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every odoo_unlink call is checked against it from then on.
Questions about odoo_unlink
Delete records by IDs. 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.
Register the Odoo Claude MCP server in PolicyLayer and add a rule for odoo_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.
odoo_unlink 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 odoo_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.
Set action: deny in the PolicyLayer policy for odoo_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.
odoo_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.
More on Odoo Claude, and thousands of servers like it.
Across the catalogue