Delete records from an Odoo model.
AI agents call odoo_delete to permanently remove resources in MCP Odoo Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs deletion operations on database records, which is irreversible and cannot be undone. This is a classic destructive action. Given that Odoo manages business-critical data (financial records, customer information, inventory), unauthorized or incorrect deletion via an AI agent could result in permanent loss of important business data with severe consequences.
From the tool's definition Tool name 'odoo_delete' and description 'Delete records from an Odoo model' explicitly indicate irreversible deletion of data from a database.
Attacks that exploit this kind of access
Delete records from an Odoo model. It is categorised as a Destructive tool in the MCP Odoo Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Odoo Server MCP server in PolicyLayer and add a rule for odoo_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 MCP Odoo Server. Nothing to install.
odoo_delete 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_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.
Set action: deny in the PolicyLayer policy for odoo_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.
odoo_delete is provided by the MCP Odoo Server MCP server (malvernbright/odoo-claude-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 →