AI agents invoke odoo_action to trigger actions in Odoo. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes named actions in Odoo, which are predefined business operations that can have side effects ranging from state transitions to record creation/modification. While the action names are constrained (not arbitrary code execution), the outcome depends on externally-provided action names and can trigger complex workflows.
From the tool's definition Tool name 'odoo_action' combined with description 'Execute a named Odoo action' indicates execution of arbitrary named actions within Odoo.
Attacks that exploit this kind of access
Execute a named Odoo action. It is categorised as a Execute tool in the Odoo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Odoo MCP server in PolicyLayer and add a rule for odoo_action: 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. Nothing to install.
odoo_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the odoo_action 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_action. 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_action is provided by the Odoo MCP server (plgonzalezrx8/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 →