删除Odoo中的记录
AI agents call delete_odoo_record to permanently remove resources in Odoo MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting records from an ERP system like Odoo is a destructive operation that cannot be undone and affects business-critical data. This poses critical risk if an AI agent executes it without proper authorization or context. Classified as Destructive (not Execute) because the action itself is inherently destructive rather than conditionally so.
From the tool's definition Tool name 'delete_odoo_record' explicitly states it deletes records. Description translates from Chinese to 'Delete records in Odoo'. Deletion is irreversible data destruction.
Attacks that exploit this kind of access
删除Odoo中的记录. It is categorised as a Destructive tool in the Odoo MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Odoo MCP Server MCP server in PolicyLayer and add a rule for delete_odoo_record: 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 MCP Server. Nothing to install.
delete_odoo_record 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 delete_odoo_record 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 delete_odoo_record. 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.
delete_odoo_record is provided by the Odoo MCP Server MCP server (kaikongbj/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 →