amocrm_create_status
A write tool on the All MCP server.
This record as markdown: /tools/allmcp/amocrm-create-status.md
What amocrm_create_status does on Allmcp
AI agents use amocrm_create_status to create or update resources in Allmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Allmcp environment.
Why amocrm_create_status is rated Medium
The 'create' action modifies data reversibly—a status can typically be updated or deleted later. This is Write category, not Destructive. Severity is medium because creating statuses in a CRM affects business workflows and could cause confusion if done incorrectly by an agent, but it's not immediately irreversible or financial. Confidence is lowered due to the empty description.
From the tool's definition Tool name 'amocrm_create_status' contains verb 'create', indicating data creation. Description is empty, limiting confidence.
Attacks that exploit this kind of access
The rule that runs amocrm_create_status 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_create_status, this is the rule to start with:
amocrm_create_status stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Allmcp, apply this rule, and every amocrm_create_status call is checked against it from then on.
Questions about amocrm_create_status
amocrm_create_status is a write tool on the All MCP server. It is categorised as a Write tool in the Allmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the All MCP server in PolicyLayer and add a rule for amocrm_create_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.
amocrm_create_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the amocrm_create_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.
Set action: deny in the PolicyLayer policy for amocrm_create_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.
amocrm_create_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.
This server
Across the catalogue