Get hierarchical tree of organizational structure (departments with nested children)
AI agents call bitrix_department_tree 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 tool retrieves organizational hierarchy information without modifying, executing operations, or deleting data. It is a straightforward read operation that queries existing data structure. The low severity reflects that organizational charts are typically non-sensitive information, and misuse would at worst result in information disclosure rather than system compromise or data loss.
From the tool's definition Tool description states 'Get hierarchical tree' which is a retrieval operation. The word 'Get' indicates a query/fetch action with no side effects. Organizational structure data is non-sensitive metadata in most contexts.
Attacks that exploit this kind of access
Get hierarchical tree of organizational structure (departments with nested children). 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_department_tree: 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_department_tree 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_department_tree 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_department_tree. 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_department_tree 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 →