execute_method · Odoo Mcp Xyt MCP: Risk & Policy

WHAT IT DOES

What execute_method does on Odoo Mcp Xyt

AI agents invoke execute_method to trigger actions in Odoo Mcp Xyt. 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

This tool allows execution of custom methods on Odoo models, which constitutes running code whose effects depend on the method arguments and implementation. While it could theoretically be limited to read-only or safe methods, the absence of such constraints in the description and the generic nature of 'custom method' execution means it could trigger destructive operations (deletes, financial transactions, data…

From the tool's definition Tool name 'execute_method' combined with description 'Execute a custom method on an Odoo model' indicates the ability to run arbitrary code or methods on an ERP system's models without explicit constraints on what those methods can do.

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 Xyt, so you can run agents against it safely.

FAQ

Questions about execute_method

What does the execute_method tool do? +

Execute a custom method on an Odoo model. It is categorised as a Execute tool in the Odoo Mcp Xyt 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 Xyt 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 Xyt. 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 Xyt MCP server (xyt-mcp/odoo-mcp-xyt). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.