Read specific records by their IDs.
AI agents call odoo_read to retrieve information from MCP Odoo Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from an Odoo database by record ID without modifying, deleting, or executing operations. It is a straightforward read operation that returns existing data. While the Odoo server overall supports destructive operations (odoo_delete, odoo_execute), this specific tool is limited to data retrieval, making it low severity.
From the tool's definition Tool name is 'odoo_read' and description explicitly states 'Read specific records by their IDs.' This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Read specific records by their IDs. It is categorised as a Read tool in the MCP Odoo Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Odoo Server 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 MCP Odoo Server. 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 MCP Odoo Server MCP server (malvernbright/odoo-claude-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →