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 tool retrieves employee records based on search criteria (name). It performs a read-only lookup operation against the Odoo ERP system with no ability to create, modify, delete, or execute code. The blast radius of misuse is minimal — an attacker gains visibility into employee information but cannot alter it or trigger external actions. Classified as Read with low severity.
From the tool's definition Tool name is 'search_employee' and description states 'Search for employees by name' — this is a query/search operation with no side effects.
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 (urmilabhuva/mcp-odoo-fork). 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 →