AI agents call search_records 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 retrieves or queries data from Odoo ERP records using filters, with no side effects on the data. It follows the 'Read' category pattern of search/list/get/fetch operations. Low severity because misuse would only expose existing data the agent has access to, not cause destructive or financial harm.
From the tool's definition Tool name 'search_records' with description 'Search records with advanced filtering' indicates a query/retrieval operation. Server context mentions 'searching employees' as an example use case. No modification, deletion, or execution keywords present.
Attacks that exploit this kind of access
Search records with advanced filtering. 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_records: 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_records 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_records 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_records. 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_records 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 →