Get user information by ID
AI agents call bitrix24_get_user to retrieve information from Bitrix24 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 user information without side effects or data modification. It is a straightforward read operation that queries existing data from the Bitrix24 CRM system based on a user ID parameter. No data is created, modified, deleted, or executed—only retrieved. Severity is low as unauthorized access to user information, while a concern, has limited blast radius in typical CRM contexts.
From the tool's definition Tool name 'bitrix24_get_user' combined with description 'Get user information by ID' indicates data retrieval. The verb 'Get' and the lack of modification, deletion, or execution language clearly indicate a query operation.
Attacks that exploit this kind of access
Get user information by ID. It is categorised as a Read tool in the Bitrix24 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bitrix24 MCP Server MCP server in PolicyLayer and add a rule for bitrix24_get_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 Bitrix24 MCP Server. Nothing to install.
bitrix24_get_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 bitrix24_get_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 bitrix24_get_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.
bitrix24_get_user is provided by the Bitrix24 MCP Server MCP server (maxli53/mcp_bitrix). 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 →