Count Odoo records matching a domain
AI agents call search_count to retrieve information from Odoo MCP 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 read-only query to count records based on filter criteria. It retrieves information without creating, modifying, or deleting any data, and does not execute arbitrary code or trigger external operations. The blast radius of misuse is minimal—an agent could only query data it already has permission to access. Confidence is high due to clear, unambiguous description.
From the tool's definition Tool name 'search_count' and description 'Count Odoo records matching a domain' indicate a query operation that retrieves aggregate data without modification. No side effects, data creation, deletion, or code execution.
Attacks that exploit this kind of access
Count Odoo records matching a domain. It is categorised as a Read tool in the Odoo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Odoo MCP Server MCP server in PolicyLayer and add a rule for search_count: 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 Server. Nothing to install.
search_count 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_count 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_count. 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_count is provided by the Odoo MCP Server MCP server (mah007/odoomcp). 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 →