Quick search for employees by name, last name, middle name, position, or department name
AI agents call bitrix_user_search to retrieve information from Email 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 search/lookup function that retrieves employee directory information. It does not create, modify, delete, execute commands, or move money. The blast radius of misuse is limited to unauthorized viewing of organizational directory data, which is low compared to other risk categories. Confidence is high because the description clearly indicates read-only behavior.
From the tool's definition Tool description states 'search for employees by name, last name, middle name, position, or department name' — a pure query operation with no modification or side effects.
Attacks that exploit this kind of access
Quick search for employees by name, last name, middle name, position, or department name. It is categorised as a Read tool in the Email MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Email MCP Server MCP server in PolicyLayer and add a rule for bitrix_user_search: 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 Email MCP Server. Nothing to install.
bitrix_user_search 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 bitrix_user_search 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 bitrix_user_search. 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.
bitrix_user_search is provided by the Email MCP Server MCP server (sventern/mcp_email). 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 →