odoo_web_call

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

SERVEROdoo Claude MCP SOURCErosenvladimirov/odoo-claude-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/odoo-web-call.md

WHAT IT DOES

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.

RISK

Why odoo_web_call is rated High

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)"

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs odoo_web_call safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Odoo Claude MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For odoo_web_call, this is the rule to start with:

odoo_web_call Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every odoo_web_call call is checked against it from then on.

FAQ

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.

KEEP EXPLORING

More on Odoo Claude, and thousands of servers like it.

This server

All 246 Odoo Claude tools → High-risk tools on this server →

Across the catalogue

call_rpc on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →