odoo_execute · MCP Odoo Server MCP: Risk & Policy

WHAT IT DOES

What odoo_execute does on MCP Odoo Server

AI agents invoke odoo_execute to trigger actions in MCP Odoo 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 odoo_execute needs a policy

This tool permits execution of arbitrary methods on Odoo models without restriction, which constitutes Execute-category behavior. The critical severity reflects that an AI agent with access could invoke destructive operations (deletions), financial transactions, module installations, or other irreversible actions depending on the specific methods available in the target Odoo instance.

From the tool's definition Tool description states 'Execute any method on an Odoo model (advanced usage)' - the term 'Execute' combined with 'any method' indicates arbitrary code execution capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

odoo_execute Rate-limited

odoo_execute 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": {
    "odoo_execute": {
      "limits": [
        {
          "counter": "odoo_execute_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 MCP Odoo Server, so you can run agents against it safely.

FAQ

Questions about odoo_execute

What does the odoo_execute tool do? +

Execute any method on an Odoo model (advanced usage). It is categorised as a Execute tool in the MCP Odoo 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 odoo_execute? +

Register the MCP Odoo Server MCP server in PolicyLayer and add a rule for odoo_execute: 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 MCP Odoo Server. Nothing to install.

What risk level is odoo_execute? +

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

Can I rate-limit odoo_execute? +

Yes. Add a rate_limit block to the odoo_execute 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 odoo_execute completely? +

Set action: deny in the PolicyLayer policy for odoo_execute. 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 odoo_execute? +

odoo_execute is provided by the MCP Odoo Server MCP server (malvernbright/odoo-claude-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.