amocrm_delete_custom_field
A destructive tool on the All MCP server.
This record as markdown: /tools/allmcp/amocrm-delete-custom-field.md
What amocrm_delete_custom_field does on Allmcp
AI agents call amocrm_delete_custom_field to permanently remove resources in Allmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why amocrm_delete_custom_field is rated Critical
delete_* operations irreversibly remove data and cannot be undone. Even though the description is missing, the combination of 'delete' verb and 'custom_field' object clearly indicates a destructive action. High blast radius if an AI agent mistakenly deletes critical custom fields in an amoCRM instance.
From the tool's definition Tool name contains 'delete' and targets 'custom_field' — indicates irreversible deletion of data. Description is empty, limiting confidence slightly but the name is unambiguous.
Attacks that exploit this kind of access
The rule that runs amocrm_delete_custom_field safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Allmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For amocrm_delete_custom_field, this is the rule to start with:
amocrm_delete_custom_field 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 Allmcp, apply this rule, and every amocrm_delete_custom_field call is checked against it from then on.
Questions about amocrm_delete_custom_field
amocrm_delete_custom_field is a destructive tool on the All MCP server. It is categorised as a Destructive tool in the Allmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the All MCP server in PolicyLayer and add a rule for amocrm_delete_custom_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 Allmcp. Nothing to install.
amocrm_delete_custom_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 amocrm_delete_custom_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 amocrm_delete_custom_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.
amocrm_delete_custom_field is provided by the All MCP server (Perception-Dynamics-Inc/allmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on All, and thousands of servers like it.
Across the catalogue