bitrix_checklist

Server Email MCP Server sventern/mcp_email

Risk class Critical

Parameters 00 required

WHAT IT DOES

What bitrix_checklist does on Email MCP Server

AI agents call bitrix_checklist to permanently remove resources in Email MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

WHY IT NEEDS A POLICY

Why bitrix_checklist needs a policy

The tool supports multiple actions including 'delete' which irreversibly removes checklist items. Per the rules, when a tool spans categories, the most severe applicable category takes precedence. Since delete is destructive (irreversible removal), the tool is classified as Destructive.

From the tool's definition delete: Delete item (requires taskId, checklistId)

Attacks that exploit this kind of access

Questions about bitrix_checklist

What does the bitrix_checklist tool do? +

Task checklist management. Actions: - add: Add checklist item (requires taskId, title) - list: List checklist items (requires taskId) - update: Update item (requires taskId, checklistId, title) - delete: Delete item (requires taskId, checklistId) - complete: Mark item complete (requires taskId, checklistId) - renew: Mark item incomplete (requires taskId, checklistId). It is categorised as a Destructive tool in the Email MCP Server 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 bitrix_checklist? +

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

bitrix_checklist 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 bitrix_checklist? +

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

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

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