execute_odoo_code · MCP Odoo Shell MCP: Risk & Policy

WHAT IT DOES

What execute_odoo_code does on MCP Odoo Shell

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

This tool executes arbitrary Python code in an Odoo database environment. Python code execution with database context access is fundamentally an Execute risk with critical severity because it can: inspect/modify any Odoo model, access sensitive business data, trigger business logic, perform destructive operations (via ORM or raw SQL), or exfiltrate information.

From the tool's definition Server description states 'allowing execution of Python code within an Odoo database context for model introspection and database operations.' Tool name is 'execute_odoo_code' which directly implies arbitrary code execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_odoo_code Rate-limited

execute_odoo_code 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_odoo_code": {
      "limits": [
        {
          "counter": "execute_odoo_code_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 Shell, so you can run agents against it safely.

FAQ

Questions about execute_odoo_code

What does the execute_odoo_code tool do? +

execute_odoo_code. It is categorised as a Execute tool in the MCP Odoo Shell 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_odoo_code? +

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

What risk level is execute_odoo_code? +

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

Can I rate-limit execute_odoo_code? +

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

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

execute_odoo_code is provided by the MCP Odoo Shell MCP server (seletz/mcp-odoo-shell). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.