Critical Risk →

bitrix24_delete_task_checklist_item

Delete a checklist item from a task

Part of the Bitrix24 Tasks MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents may call bitrix24_delete_task_checklist_item to permanently remove or destroy resources in Bitrix24 Tasks. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call bitrix24_delete_task_checklist_item in a loop, permanently destroying resources in Bitrix24 Tasks. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

bitrix24-tasks.yaml
tools:
  bitrix24_delete_task_checklist_item:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Bitrix24 Tasks policy for all 23 tools.

Tool Name bitrix24_delete_task_checklist_item
Category Destructive
Risk Level Critical

View all 23 tools →

Agents calling destructive-class tools like bitrix24_delete_task_checklist_item have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

bitrix24_delete_task_checklist_item is one of the critical-risk operations in Bitrix24 Tasks. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the bitrix24_delete_task_checklist_item tool do? +

Delete a checklist item from a task. It is categorised as a Destructive tool in the Bitrix24 Tasks MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on bitrix24_delete_task_checklist_item? +

Add a rule in your Intercept YAML policy under the tools section for bitrix24_delete_task_checklist_item. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Bitrix24 Tasks MCP server.

What risk level is bitrix24_delete_task_checklist_item? +

bitrix24_delete_task_checklist_item is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit bitrix24_delete_task_checklist_item? +

Yes. Add a rate_limit block to the bitrix24_delete_task_checklist_item rule in your Intercept 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.

How do I block bitrix24_delete_task_checklist_item completely? +

Set action: deny in the Intercept policy for bitrix24_delete_task_checklist_item. 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.

What MCP server provides bitrix24_delete_task_checklist_item? +

bitrix24_delete_task_checklist_item is provided by the Bitrix24 Tasks MCP server (bitrix24-tasks-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.