bitrix_user_by_department

Get all employees from a specific department (with optional recursive search in child departments)

Server Email MCP Server sventern/mcp_email
Category Read
Risk class Low
Parameters 00 required

What bitrix_user_by_department does on Email MCP Server

AI agents call bitrix_user_by_department 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.

Why bitrix_user_by_department needs a policy

This tool retrieves organizational directory information (employees in a department). It performs a read-only query with no ability to modify, delete, or execute code. Even though it may return multiple records, the blast radius of misuse is low — an AI agent could enumerate staff but cannot harm systems, finances, or data integrity. Low severity assigned.

From the tool's definition Tool description explicitly states 'Get all employees from a specific department' — a query operation that retrieves data without modification or side effects.

Questions about bitrix_user_by_department

What does the bitrix_user_by_department tool do? +

Get all employees from a specific department (with optional recursive search in child departments). It is categorised as a Read tool in the Email MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bitrix_user_by_department? +

Register the Email MCP Server MCP server in PolicyLayer and add a rule for bitrix_user_by_department: 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.

What risk level is bitrix_user_by_department? +

bitrix_user_by_department is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bitrix_user_by_department? +

Yes. Add a rate_limit block to the bitrix_user_by_department 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.

How do I block bitrix_user_by_department completely? +

Set action: deny in the PolicyLayer policy for bitrix_user_by_department. 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.

What MCP server provides bitrix_user_by_department? +

bitrix_user_by_department 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.