AI agents call getUser 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.
The tool appears to fetch user information from the Bitrix24 CRM. With no description provided, classification relies on naming conventions and consistency with sibling tools. This is a query/retrieval operation with no side effects, making it a Read action.
From the tool's definition Tool name 'getUser' indicates a retrieval operation with no destructive or modification suffix. Consistent with sibling Read tools like 'getContact', 'getContacts', 'getActivity', 'getActivities', and 'getCallStatistics' on the same CRM server.
Documented attack patterns abuse exactly the kind of access getUser gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bitrix24 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getUser:
{
"version": "1",
"default": "deny",
"tools": {
"getUser": {}
}
}getUser is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
getUser. 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 getUser: 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.
getUser 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 getUser 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 getUser. 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.
getUser is provided by the Bitrix24 MCP Server MCP server (oneatdrt/bitrix24_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bitrix24 MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 Bitrix24 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.