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

amocrm_update_custom_field

A write tool on the All MCP server.

SERVERAllmcp SOURCEPerception-Dynamics-Inc/allmcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/allmcp/amocrm-update-custom-field.md

What amocrm_update_custom_field does on Allmcp

AI agents use amocrm_update_custom_field 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_custom_field is rated Medium

The 'update' verb clearly indicates a write operation that modifies existing data reversibly. While the empty description reduces confidence, the tool name strongly suggests it updates custom fields in an AmoCRM system, which is a data modification action characteristic of the Write category. Severity is medium because updates can corrupt data or cause business logic issues, but are typically reversible.

From the tool's definition Tool name 'amocrm_update_custom_field' indicates modification of data via an 'update' operation. Description is empty, limiting evidence specificity.

Questions about amocrm_update_custom_field

What does the amocrm_update_custom_field tool do? +

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

How do I enforce a policy on amocrm_update_custom_field? +

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

What risk level is amocrm_update_custom_field? +

amocrm_update_custom_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit amocrm_update_custom_field? +

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

How do I block amocrm_update_custom_field completely? +

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

What MCP server provides amocrm_update_custom_field? +

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

This server

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