bitrix_checklist_complete · Email MCP Server MCP

WHAT IT DOES

What bitrix_checklist_complete does on Email MCP Server

AI agents use bitrix_checklist_complete 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_complete needs a policy

This tool modifies data by changing a checklist item's completion status. It is categorized as Write rather than Execute because it performs a specific data state change rather than executing arbitrary code or commands. It is reversible (not Destructive) since completion status can typically be toggled.

From the tool's definition Tool performs 'Mark a checklist item as completed', which modifies the state of an existing checklist item in Bitrix24. This is a reversible data modification operation (the item can be marked incomplete again).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bitrix_checklist_complete Rate-limited

bitrix_checklist_complete 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_complete": {
      "limits": [
        {
          "counter": "bitrix_checklist_complete_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_complete

What does the bitrix_checklist_complete tool do? +

Mark a checklist item as completed 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_complete? +

Register the Email MCP Server MCP server in PolicyLayer and add a rule for bitrix_checklist_complete: 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_complete? +

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

Can I rate-limit bitrix_checklist_complete? +

Yes. Add a rate_limit block to the bitrix_checklist_complete 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_complete completely? +

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

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