High Risk →

odoo_web_call

Call any Odoo model method via web session (JSON-RPC /web/dataset/call_kw).

How to control odoo_web_call ↓

What odoo_web_call does on Odoo Claude MCP

AI agents invoke odoo_web_call to trigger actions in Odoo Claude MCP. 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.

High Risk

Why odoo_web_call needs a policy

This tool can invoke arbitrary Odoo model methods via JSON-RPC, meaning it can trigger any operation on any model — including reads, writes, deletes, financial transactions, and custom business logic.

From the tool's definition "Call any Odoo model method via web session (JSON-RPC /web/dataset/call_kw)"

Documented attack patterns abuse exactly the kind of access odoo_web_call gives an agent:

How to control odoo_web_call

PolicyLayer is an MCP gateway — it sits between your AI agents and Odoo Claude MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for odoo_web_call:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "odoo_web_call": {
      "limits": [
        {
          "counter": "odoo_web_call_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

odoo_web_call 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.

  1. Create a free account and register Odoo Claude MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about odoo_web_call

What does the odoo_web_call tool do? +

Call any Odoo model method via web session (JSON-RPC /web/dataset/call_kw). It is categorised as a Execute tool in the Odoo Claude MCP 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_web_call? +

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

What risk level is odoo_web_call? +

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

Can I rate-limit odoo_web_call? +

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

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

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

Enforce policy on every Odoo Claude MCP tool call.

Start from Odoo Claude MCP, 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.

180 Odoo Claude MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.