Universal list (infoblock) management. Actions: - add: Create list (requires iblockTypeId, iblockCode, name) - get: Get list(s) (requires iblockTypeId) - update: Update list (requires iblockTypeId and iblockId or iblockCode) - delete: Delete list (requires iblockTypeId and iblockId or iblockCode)...
AI agents call bitrix_list 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 supports multiple actions including delete, which irreversibly removes a list/infoblock. Per the rules, when a tool spans categories, the most severe applies — Destructive takes precedence over Write (add/update) and Read (get) actions available in this same tool.
From the tool's definition delete: Delete list (requires iblockTypeId and iblockId or iblockCode)
Attacks that exploit this kind of access
Universal list (infoblock) management. Actions: - add: Create list (requires iblockTypeId, iblockCode, name) - get: Get list(s) (requires iblockTypeId) - update: Update list (requires iblockTypeId and iblockId or iblockCode) - delete: Delete list (requires iblockTypeId and iblockId or iblockCode) - get_iblock_type: Get infoblock type identifier. 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_list: 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_list 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_list 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_list. 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_list 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.
bitrix_list is one line of Email MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →