Diagnose webhook permissions and access to different CRM entities
AI agents call bitrix24_diagnose_permissions 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 and reports permission and access information about CRM entities and webhooks. It performs a diagnostic read operation with no side effects—it does not create, modify, delete, or execute external actions. The most severe risk is information disclosure of permission status, which is a low-severity read operation in a CRM context where such diagnostic queries are routine administrative activities.
From the tool's definition Tool name and description indicate it 'diagnose[s] webhook permissions and access' — a diagnostic/informational operation that queries permission status without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Diagnose webhook permissions and access to different CRM entities. 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_diagnose_permissions: 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_diagnose_permissions 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_diagnose_permissions 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_diagnose_permissions. 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_diagnose_permissions 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 →