User/employee management. Actions: - list: List all users with filters - get: Get user by ID (requires userId) - get_many: Get multiple users by IDs (requires userIds) - current: Get current user (webhook owner) - search: Search users (requires query) - fields: Get available user fields - by_depa...
AI agents call bitrix_user 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.
The bitrix_user tool provides user/employee lookup and filtering functionality without any side effects. All documented actions (list, get, search, etc.) are data retrieval operations.
From the tool's definition Tool description lists only retrieval operations: 'list', 'get', 'get_many', 'current', 'search', 'fields', 'by_department'. All are read-only queries with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
User/employee management. Actions: - list: List all users with filters - get: Get user by ID (requires userId) - get_many: Get multiple users by IDs (requires userIds) - current: Get current user (webhook owner) - search: Search users (requires query) - fields: Get available user fields - by_department: Get users by department (requires departmentId). 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: 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 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 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. 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 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 →