Search for records in an Odoo model. Returns record IDs matching the domain.
AI agents call odoo_search 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 performs a query operation to retrieve matching record IDs based on search criteria (domain). It has no side effects—it does not create, modify, delete, execute code, or move money. While the Odoo server supports destructive and financial operations via sibling tools, odoo_search itself is purely a Read operation with minimal blast radius.
From the tool's definition Tool name 'odoo_search' and description 'Search for records in an Odoo model. Returns record IDs matching the domain.' indicate a search operation that retrieves data without modification.
Attacks that exploit this kind of access
Search for records in an Odoo model. Returns record IDs matching the domain. 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_search: 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_search 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 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. 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 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 →