Count records matching domain in Odoo model
AI agents call odoo_search_count 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.
This tool performs a read-only operation that counts records based on search criteria. It has no side effects, creates no modifications, executes no arbitrary code, and destroys no data. The blast radius of misuse is minimal—an attacker could only learn aggregate information about record counts. This is classic Read category behavior (search/query with no mutations).
From the tool's definition Tool name 'odoo_search_count' and description 'Count records matching domain in Odoo model' indicate a query/retrieval operation that returns a count of matching records without modifying data.
Attacks that exploit this kind of access
Count records matching domain in Odoo model. 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_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 XML-RPC MCP Server. Nothing to install.
odoo_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 odoo_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 odoo_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.
odoo_search_count 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 →