Search and read records in one call
AI agents call odoo_search_read to retrieve information from Odoo XML-RPC MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs two read-only operations: searching for records matching criteria and reading their data. It retrieves and queries data without creating, modifying, or deleting records. The sibling tools odoo_create, odoo_write, and odoo_unlink handle write/destructive operations separately. A misused search_read operation cannot irreversibly change or delete data, making it a low-severity read operation.
From the tool's definition Tool name 'odoo_search_read' and description 'Search and read records in one call' indicate a combined search-and-retrieve operation with no modification or deletion semantics.
Attacks that exploit this kind of access
Search and read records in one call. It is categorised as a Read tool in the Odoo XML-RPC MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Odoo XML-RPC MCP Server MCP server in PolicyLayer and add a rule for odoo_search_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 XML-RPC MCP Server. Nothing to install.
odoo_search_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_search_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_search_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_search_read is provided by the Odoo XML-RPC MCP Server MCP server (odoo-dgoo2308/xml-rpc-odoo-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 →