AI agents use odoo_create_sale_order to create or update resources in Odooclaw — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Odooclaw environment.
This tool creates new data (a sale order) which is a reversible operation typical of Write category. However, sale orders in ERP systems are business-critical documents that trigger downstream financial processes (invoicing, payments, inventory allocation). Misuse could commit the organization to unwanted sales obligations.
From the tool's definition 'Creates a sale order (presupuesto) for a customer with product lines' - the tool generates and persists a new financial document in the ERP system
Attacks that exploit this kind of access
Creates a sale order (presupuesto) for a customer with product lines. It is categorised as a Write tool in the Odooclaw MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Odooclaw MCP server in PolicyLayer and add a rule for odoo_create_sale_order: 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 Odooclaw. Nothing to install.
odoo_create_sale_order is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the odoo_create_sale_order 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_create_sale_order. 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_create_sale_order is provided by the Odooclaw MCP server (nicolasramos/odooclaw-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 →