Create a new deal in Bitrix24 CRM
AI agents use bitrix24_create_deal to create or update resources in Bitrix24 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bitrix24 MCP Server environment.
This tool creates new deal records in a CRM system, which modifies business data. While creation is reversible (deals can be deleted), the primary action is to write/create new data entities. This is classified as Write rather than Execute because it creates structured CRM entities rather than executing arbitrary code or commands.
From the tool's definition Tool name contains 'create' and description states 'Create a new deal in Bitrix24 CRM', indicating irreversible data creation in a business system.
Attacks that exploit this kind of access
Create a new deal in Bitrix24 CRM. It is categorised as a Write tool in the Bitrix24 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bitrix24 MCP Server MCP server in PolicyLayer and add a rule for bitrix24_create_deal: 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_create_deal is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bitrix24_create_deal 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_create_deal. 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_create_deal 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 →