amocrm_delete_pipeline
Delete a pipeline (only if empty — AmoCRM rejects deletes with leads).
This record as markdown: /tools/allmcp/amocrm-delete-pipeline.md
What amocrm_delete_pipeline does on Allmcp
AI agents call amocrm_delete_pipeline 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_pipeline is rated Critical
This tool permanently removes a pipeline from AmoCRM. Although AmoCRM enforces a precondition (empty pipelines only), the action itself is destructive and cannot be undone. Deletion of business-critical configuration like pipelines warrants Destructive classification over Execute, as it irreversibly alters system state.
From the tool's definition Tool name contains 'delete' and description states 'Delete a pipeline'. Even though constrained to empty pipelines, deletion is irreversible.
Attacks that exploit this kind of access
The rule that runs amocrm_delete_pipeline 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_pipeline, this is the rule to start with:
amocrm_delete_pipeline 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_pipeline call is checked against it from then on.
Questions about amocrm_delete_pipeline
Delete a pipeline (only if empty — AmoCRM rejects deletes with leads). 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_pipeline: 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_pipeline 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_pipeline 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_pipeline. 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_pipeline 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