AI agents call search_by_name to retrieve information from Odoo-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search operation using name_search, a standard Odoo RPC method that queries records and returns results. It has no side effects—it does not create, modify, delete, or execute code. The blast radius is minimal since it only retrieves data. Despite being part of a system with access to Odoo models and records, this specific tool is limited to read-only functionality.
From the tool's definition Tool name 'search_by_name' and description 'Search records by name (name_search)' indicate a query operation that retrieves matching records without modifying data.
Attacks that exploit this kind of access
Search records by name (name_search). It is categorised as a Read tool in the Odoo-MCP MCP Server, which means it retrieves data without modifying state.
Register the Odoo- MCP server in PolicyLayer and add a rule for search_by_name: 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-MCP. Nothing to install.
search_by_name 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 search_by_name 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 search_by_name. 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.
search_by_name is provided by the Odoo- MCP server (ridrisa/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 →