Get task counters (statistics) for a user in Bitrix24
AI agents call bitrix_task_counters 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 retrieves statistical information (task counters) for a user. It performs a read-only query operation that returns data without altering state, executing code, or affecting external systems. No data is created, modified, deleted, or moved, making it a straightforward Read category tool with low risk of misuse.
From the tool's definition Tool name includes 'counters' and description states 'Get task counters (statistics)' — a retrieval operation with no modification, deletion, or execution. Returns aggregate data about tasks without side effects.
Attacks that exploit this kind of access
Get task counters (statistics) for a user in Bitrix24. 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_task_counters: 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_task_counters 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_task_counters 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_task_counters. 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_task_counters 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 →