This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/odoo-read.md
What odoo_read does on Odoo Claude MCP
AI agents call odoo_read to retrieve information from Odoo Claude MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why odoo_read is rated Low
This tool performs a query operation to retrieve data from Odoo records identified by their IDs. There is no mention of creating, modifying, deleting, or executing any operations—it is purely a data retrieval function. This is a classic Read operation with minimal risk, unless the retrieved data is sensitive, but that is a data sensitivity issue rather than a tool capability issue.
From the tool's definition Tool name 'odoo_read' and description 'Read specific records by IDs' explicitly indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs odoo_read 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_read, this is the rule to start with:
odoo_read is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every odoo_read call is checked against it from then on.
Questions about odoo_read
Read specific records by IDs. It is categorised as a Read tool in the Odoo Claude MCP MCP Server, which means it retrieves data without modifying state.
Register the Odoo Claude MCP server in PolicyLayer and add a rule for odoo_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.
odoo_read is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the odoo_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.
Set action: deny in the PolicyLayer policy for odoo_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.
odoo_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.
More on Odoo Claude, and thousands of servers like it.
This server
Across the catalogue