Test connection to Bitrix24 API and get current user info
AI agents call bitrix_test_connection 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 performs a diagnostic read operation to verify connectivity and retrieve metadata about the authenticated user. It has no ability to modify data, execute arbitrary code, or incur financial obligations. The blast radius of misuse is minimal — at worst, an attacker could learn basic user identity information. Low severity is appropriate for a read-only diagnostic function.
From the tool's definition Tool description states 'Test connection to Bitrix24 API and get current user info' — it retrieves user information without modifying, deleting, or executing operations with side effects.
Attacks that exploit this kind of access
Test connection to Bitrix24 API and get current user info. 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_test_connection: 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_test_connection 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_test_connection 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_test_connection. 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_test_connection 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 →