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 without explicit specification of what those methods do. While the sibling tools (create_record, delete_record, etc.) are explicit about their operations, execute_method's outcome is method-dependent and unpredictable to the AI agent.
From the tool's definition Tool name 'execute_method' combined with description 'Execute custom methods on Odoo models' directly indicates arbitrary code execution capability.
Documented attack patterns abuse exactly the kind of access execute_method gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Odoo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_method:
{
"version": "1",
"default": "deny",
"tools": {
"execute_method": {
"limits": [
{
"counter": "execute_method_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_method stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute custom methods on Odoo models. 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 (vzeman/odoo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Odoo MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Odoo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.