Get change history for a task in Bitrix24
AI agents call bitrix_task_history 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 historical audit/change data from a task object. It performs no writes, deletions, or execution of code. The information retrieved is metadata about past changes, not sensitive user data like email content. The blast radius of misuse is minimal—an attacker could view task history they may not be authorized to see, but cannot modify data or trigger actions.
From the tool's definition Tool name 'bitrix_task_history' and description 'Get change history for a task in Bitrix24' indicate a retrieval operation. The verb 'Get' and the absence of any modification, deletion, or execution language confirm this is a read-only query.
Attacks that exploit this kind of access
Get change history for a task 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_history: 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_history 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_history 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_history. 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_history 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 →