amocrm_update_customer
A write tool on the All MCP server.
This record as markdown: /tools/allmcp/amocrm-update-customer.md
What amocrm_update_customer does on Allmcp
AI agents use amocrm_update_customer 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_update_customer is rated Medium
The tool performs a reversible update operation on customer records ('update_customer'). This is a Write operation rather than Destructive (not deleting), Execute (not running arbitrary code), or Read (actively modifying, not just retrieving).
From the tool's definition Tool name 'amocrm_update_customer' indicates modification of customer data. Description is empty, limiting direct evidence.
Attacks that exploit this kind of access
The rule that runs amocrm_update_customer 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_update_customer, this is the rule to start with:
amocrm_update_customer 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_update_customer call is checked against it from then on.
Questions about amocrm_update_customer
amocrm_update_customer 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_update_customer: 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_update_customer 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_update_customer 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_update_customer. 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_update_customer 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