Search for employees by name
AI agents call search_employee 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 is a straightforward read operation that searches and retrieves employee records based on name criteria. It has no side effects, does not execute code, does not modify data, and does not involve financial operations. The blast radius of misuse is minimal—an AI agent could only retrieve employee information that may already be accessible through normal Odoo access controls.
From the tool's definition Tool name 'search_employee' and description 'Search for employees by name' indicate a query operation that retrieves employee data without modifying or deleting it.
Attacks that exploit this kind of access
Search for employees by name. 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_employee: 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_employee 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_employee 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_employee. 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_employee is provided by the Odoo MCP Server MCP server (pypi:odoo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.