List section management. Actions: - add: Create section (requires iblockTypeId, sectionCode, name) - get: Get section(s) (requires iblockTypeId) - update: Update section (requires iblockTypeId, sectionId or sectionCode) - delete: Delete section (requires iblockTypeId, sectionId or sectionCode)
AI agents call bitrix_list_section 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 operations including delete, which irreversibly removes a section. Per the rules, the most severe applicable category must be chosen. Since deletion is irreversible, this classifies as Destructive. The blast radius is high because deleting a section in a CMS/CRM like Bitrix24 can remove hierarchical content structures and all associated data.
From the tool's definition delete: Delete section (requires iblockTypeId, sectionId or sectionCode)
Attacks that exploit this kind of access
List section management. Actions: - add: Create section (requires iblockTypeId, sectionCode, name) - get: Get section(s) (requires iblockTypeId) - update: Update section (requires iblockTypeId, sectionId or sectionCode) - delete: Delete section (requires iblockTypeId, sectionId or sectionCode). 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: 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 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 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. 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 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 →