Add a new checklist item to a task in Bitrix24
AI agents use bitrix_checklist_add to create or update resources in Email MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Email MCP Server environment.
This tool creates new data (checklist items) within a task management system, but the operation is reversible—items can be deleted or modified later. It does not permanently destroy data, execute arbitrary code, move money, or retrieve information without side effects. It falls squarely into the Write category.
From the tool's definition Tool name 'bitrix_checklist_add' and description 'Add a new checklist item to a task in Bitrix24' indicate creation of data. The verb 'Add' and context of creating checklist items represent reversible data modification typical of Write operations.
Attacks that exploit this kind of access
Add a new checklist item to a task in Bitrix24. It is categorised as a Write tool in the Email MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Email MCP Server MCP server in PolicyLayer and add a rule for bitrix_checklist_add: 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_checklist_add 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 bitrix_checklist_add 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_checklist_add. 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_checklist_add 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 →