Execute a custom method on an Odoo model
AI agents invoke execute_method to trigger actions in Odoo MCP Server. 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 allows running arbitrary custom methods on Odoo models, which can trigger side effects including data modification, deletion, external API calls, or other operations depending on what custom methods exist in the target Odoo system. While not inherently destructive, the execution capability is wide-open and the blast radius is high given Odoo's integration with financial, inventory, and operational systems.
From the tool's definition Tool name 'execute_method' combined with description 'Execute a custom method on an Odoo model' explicitly indicates execution of arbitrary custom functions on Odoo ERP models through XML-RPC.
Attacks that exploit this kind of access
Execute a custom method on an Odoo model. It is categorised as a Execute tool in the Odoo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Odoo MCP Server MCP server in PolicyLayer and add a rule for execute_method: 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.
execute_method 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 execute_method 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 execute_method. 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.
execute_method is provided by the Odoo MCP Server MCP server (urmilabhuva/mcp-odoo-fork). 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 →