AI agents call getLeadStatuses 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 lead status data with no side effects. It queries reference data (likely a dropdown or enum list) from the CRM, consistent with Read operations. The absence of description reduces confidence slightly, but the naming pattern aligns with other retrieval tools on the server (getActivities, getActivity, getContact, getContacts).
From the tool's definition Tool name 'getLeadStatuses' indicates retrieval of status enumeration or metadata for leads. No description provided, but the 'get' prefix and 'Statuses' noun suggest a read-only query operation.
Documented attack patterns abuse exactly the kind of access getLeadStatuses 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 getLeadStatuses:
{
"version": "1",
"default": "deny",
"tools": {
"getLeadStatuses": {}
}
}getLeadStatuses 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.
getLeadStatuses. 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 getLeadStatuses: 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.
getLeadStatuses 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 getLeadStatuses 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 getLeadStatuses. 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.
getLeadStatuses 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.