Track deal progression through pipeline stages with timing analysis
AI agents call bitrix24_track_deal_progression 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 analyzes deal progression data (which stages deals are in, timing metrics) but does not create, modify, delete, or execute external actions. It is a pure read operation for monitoring and analytics purposes, with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name includes 'track' and description states 'Track deal progression through pipeline stages with timing analysis' — these are query/monitoring operations that retrieve and analyze existing deal data without modification.
Attacks that exploit this kind of access
Track deal progression through pipeline stages with timing analysis. 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_track_deal_progression: 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_track_deal_progression 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_track_deal_progression 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_track_deal_progression. 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_track_deal_progression 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 →