List field management. Actions: - add: Create field (requires iblockTypeId, name, type) - get: Get field(s) (requires iblockTypeId) - update: Update field (requires iblockTypeId, fieldId) - delete: Delete field (requires iblockTypeId, fieldId) - types: Get available field types (requires iblockTy...
AI agents call bitrix_list_field 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 deletion of fields, which is likely irreversible. Per the rules, when a tool spans categories, the most severe applicable category must be chosen. Deleting a field in a list/iblock context would remove the field definition and potentially all associated data, making this Destructive.
From the tool's definition Actions include 'delete: Delete field (requires iblockTypeId, fieldId)' alongside add, get, update, and types operations
Attacks that exploit this kind of access
List field management. Actions: - add: Create field (requires iblockTypeId, name, type) - get: Get field(s) (requires iblockTypeId) - update: Update field (requires iblockTypeId, fieldId) - delete: Delete field (requires iblockTypeId, fieldId) - types: Get available field types (requires iblockTypeId). 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_field: 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_field 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_field 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_field. 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_field 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 →