Task management tool. Actions: - create: Create new task (requires title, responsibleId) - get: Get task by ID (requires taskId) - list: List tasks with filters - update: Update task (requires taskId) - delete: Delete task (requires taskId) - start/pause/complete/defer/renew: Change task status (...
AI agents call bitrix_task 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.
The tool includes a 'delete' action that irreversibly removes tasks. Since the most severe applicable category must be chosen, and deletion is a destructive/irreversible operation, this tool is classified as Destructive. The blast radius is high because an AI agent could delete tasks across a task management system, potentially affecting business-critical workflows and losing data that cannot be recovered.
From the tool's definition delete: Delete task (requires taskId)
Attacks that exploit this kind of access
Task management tool. Actions: - create: Create new task (requires title, responsibleId) - get: Get task by ID (requires taskId) - list: List tasks with filters - update: Update task (requires taskId) - delete: Delete task (requires taskId) - start/pause/complete/defer/renew: Change task status (requires taskId) - approve/disapprove: Accept/reject completed task (requires taskId) - delegate: Delegate task (requires taskId, newResponsibleId) - attach_files: Attach files (requires taskId, fileIds) - counters: Get task counters - history: Get task history (requires taskId) - favorite_add/favorite_remove: Manage favorites (requires taskId) - get_fields: Get available task fields. 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.
Register the Email MCP Server MCP server in PolicyLayer and add a rule for bitrix_task: 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_task is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the bitrix_task 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_task. 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_task 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 →