bulk_delete_custom_fields
Delete multiple custom field definitions at once (max 100)
This record as markdown: /tools/instantkom-mcp-server/bulk-delete-custom-fields.md
What bulk_delete_custom_fields does on instantKOM MCP Server
AI agents call bulk_delete_custom_fields to permanently remove resources in instantKOM MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why bulk_delete_custom_fields is rated Critical
This tool permanently removes custom field definitions from the instantKOM platform. Deletion of field definitions is a destructive operation that cannot be undone and affects data structure integrity across the system. The ability to delete up to 100 definitions at once amplifies the blast radius.
From the tool's definition 'Delete multiple custom field definitions at once' — irreversibly removes data structures; uses the verb 'Delete' which signals permanent removal without recovery option.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bulk_delete_custom_fields safely
PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bulk_delete_custom_fields, this is the rule to start with:
bulk_delete_custom_fields is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect instantKOM MCP Server, apply this rule, and every bulk_delete_custom_fields call is checked against it from then on.
Questions about bulk_delete_custom_fields
Delete multiple custom field definitions at once (max 100). It is categorised as a Destructive tool in the instantKOM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for bulk_delete_custom_fields: 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 instantKOM MCP Server. Nothing to install.
bulk_delete_custom_fields 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 bulk_delete_custom_fields 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 bulk_delete_custom_fields. 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.
bulk_delete_custom_fields is provided by the instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on instantKOM MCP Server, and thousands of servers like it.
Across the catalogue