Delete a list section
AI agents call bitrix_list_section_delete 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.
Deleting a list section removes it and likely all associated content permanently. This matches the Destructive category as it cannot be undone. The blast radius is high since an entire section (and potentially its nested items) would be lost.
From the tool's definition 'Delete a list section' — the tool explicitly deletes a section of a list, which is an irreversible destructive operation.
Attacks that exploit this kind of access
Delete a list section. 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_section_delete: 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_section_delete 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_section_delete 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_section_delete. 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_section_delete 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_section_delete 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 →