execute_method · Odoo MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute_method does on Odoo MCP Server

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.

WHY IT NEEDS A POLICY

Why execute_method needs a policy

Although the tool name and description do not explicitly state code execution, the ability to call 'any method' on Odoo models is functionally equivalent to code execution in an ERP context. Odoo models expose methods that perform financial operations (e.g., validate invoices, confirm orders), destructive operations (data purges), and external integrations.

From the tool's definition Tool description states 'Call any method on Odoo model' — this permits arbitrary method invocation on ERP objects, which could trigger unintended side effects including financial transactions, data destruction, or system-level operations depending on what…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_method Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_method": {
      "limits": [
        {
          "counter": "execute_method_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Odoo MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_method

What does the execute_method tool do? +

Call any 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.

How do I enforce a policy on execute_method? +

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.

What risk level is execute_method? +

execute_method is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_method? +

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.

How do I block execute_method completely? +

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.

What MCP server provides execute_method? +

execute_method is provided by the Odoo MCP Server MCP server (mah007/odoomcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.