odoo_stock_mo_delete_draft
Safely DELETE a draft or cancelled mrp.production with cascade (raw stock.moves,
This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/odoo-stock-mo-delete-draft.md
What odoo_stock_mo_delete_draft does on Odoo Claude MCP
AI agents call odoo_stock_mo_delete_draft 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_stock_mo_delete_draft is rated Critical
This tool irreversibly deletes manufacturing order records and cascades deletion to related stock movements. Even though limited to draft/cancelled states, the cascading delete across multiple linked records and inability to undo the operation classifies it as Destructive. The high severity reflects the potential to lose manufacturing and inventory data if misused by an agent.
From the tool's definition Tool name contains 'delete', description states 'Safely DELETE a draft or cancelled mrp.production with cascade (raw stock.moves' — explicitly performs deletion with cascading effects across related records.
Attacks that exploit this kind of access
The rule that runs odoo_stock_mo_delete_draft 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_stock_mo_delete_draft, this is the rule to start with:
odoo_stock_mo_delete_draft 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_stock_mo_delete_draft call is checked against it from then on.
Questions about odoo_stock_mo_delete_draft
Safely DELETE a draft or cancelled mrp.production with cascade (raw stock.moves,. 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_stock_mo_delete_draft: 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_stock_mo_delete_draft 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_stock_mo_delete_draft 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_stock_mo_delete_draft. 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_stock_mo_delete_draft 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