New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

amocrm_delete_status

A destructive tool on the All MCP server.

SERVERAllmcp SOURCEPerception-Dynamics-Inc/allmcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/allmcp/amocrm-delete-status.md

What amocrm_delete_status does on Allmcp

AI agents call amocrm_delete_status 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_status is rated Critical

The 'delete' verb in the tool name indicates an irreversible operation that removes or destroys data (a status record in what appears to be a CRM system). This cannot be undone without external recovery. Destructive actions pose high risk because an AI agent could permanently delete critical business statuses, affecting workflows and records.

From the tool's definition Tool name 'amocrm_delete_status' contains the verb 'delete', indicating irreversible removal of data. Description is empty, limiting full context but the name is unambiguous.

Questions about amocrm_delete_status

What does the amocrm_delete_status tool do? +

amocrm_delete_status 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.

How do I enforce a policy on amocrm_delete_status? +

Register the All MCP server in PolicyLayer and add a rule for amocrm_delete_status: 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.

What risk level is amocrm_delete_status? +

amocrm_delete_status is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit amocrm_delete_status? +

Yes. Add a rate_limit block to the amocrm_delete_status 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.

How do I block amocrm_delete_status completely? +

Set action: deny in the PolicyLayer policy for amocrm_delete_status. 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.

What MCP server provides amocrm_delete_status? +

amocrm_delete_status 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of All's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.