Delete records from Odoo model
AI agents call odoo_unlink to permanently remove resources in Odoo XML-RPC MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes records from an Odoo database without possibility of reversal through normal means. Deletion is irreversible and represents maximum data loss risk. An AI agent with access to this tool could delete critical business records, customer data, transactions, or configuration across any Odoo model based on incorrect reasoning or malicious instruction.
From the tool's definition Tool name is 'odoo_unlink' and description states 'Delete records from Odoo model'. The term 'unlink' in Odoo is the standard method for irreversible deletion of records.
Attacks that exploit this kind of access
Delete records from Odoo model. It is categorised as a Destructive tool in the Odoo XML-RPC MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Odoo XML-RPC MCP Server 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 XML-RPC MCP Server. 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 XML-RPC MCP Server MCP server (odoo-dgoo2308/xml-rpc-odoo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →