bitrix_checklist_update · Email MCP Server MCP

WHAT IT DOES

What bitrix_checklist_update does on Email MCP Server

AI agents use bitrix_checklist_update 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.

WHY IT NEEDS A POLICY

Why bitrix_checklist_update needs a policy

This tool creates or modifies data reversibly by updating an existing checklist item. It is not destructive (no deletion), not financial, and not code execution. The severity is medium because checklist item modifications in a business system like Bitrix24 could disrupt workflows or task tracking if misused by an AI agent, but the changes are reversible through subsequent updates.

From the tool's definition Tool name contains 'update' and description states 'Update a checklist item in Bitrix24', indicating modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bitrix_checklist_update Rate-limited

bitrix_checklist_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bitrix_checklist_update": {
      "limits": [
        {
          "counter": "bitrix_checklist_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Email MCP Server, so you can run agents against it safely.

FAQ

Questions about bitrix_checklist_update

What does the bitrix_checklist_update tool do? +

Update a checklist item 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.

How do I enforce a policy on bitrix_checklist_update? +

Register the Email MCP Server MCP server in PolicyLayer and add a rule for bitrix_checklist_update: 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.

What risk level is bitrix_checklist_update? +

bitrix_checklist_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit bitrix_checklist_update? +

Yes. Add a rate_limit block to the bitrix_checklist_update 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.

How do I block bitrix_checklist_update completely? +

Set action: deny in the PolicyLayer policy for bitrix_checklist_update. 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 bitrix_checklist_update? +

bitrix_checklist_update 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.