Low Risk

odoo_web_read

Search and read records via web session (frontend web_search_read format).

How to control odoo_web_read ↓

What odoo_web_read does on Odoo Claude MCP

AI agents call odoo_web_read to retrieve information from Odoo Claude MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why odoo_web_read needs a policy

This tool performs data retrieval operations only (search and read). It has no side effects, does not modify or delete data, does not execute code, and does not involve financial transactions. The blast radius of misuse is limited to unauthorized information disclosure, which is a low-severity read access concern.

From the tool's definition Tool name explicitly contains 'read' and description states 'Search and read records' with no mention of modification, deletion, or execution capabilities. The format reference 'web_search_read' is a standard Odoo frontend search-and-retrieve operation.

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

How to control odoo_web_read

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_read:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "odoo_web_read": {}
  }
}

odoo_web_read is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about odoo_web_read

What does the odoo_web_read tool do? +

Search and read records via web session (frontend web_search_read format). It is categorised as a Read tool in the Odoo Claude MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on odoo_web_read? +

Register the Odoo Claude MCP server in PolicyLayer and add a rule for odoo_web_read: 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_read? +

odoo_web_read is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit odoo_web_read? +

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

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

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