amocrm_tag_contact
A write tool on the All MCP server.
This record as markdown: /tools/allmcp/amocrm-tag-contact.md
What amocrm_tag_contact does on Allmcp
AI agents use amocrm_tag_contact 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_tag_contact is rated Medium
The description is empty, so classification is based solely on the name. 'Tag' implies adding a label or tag to a contact record, which is a reversible write operation. Severity is medium as misuse could pollute CRM data at scale, but confidence is low due to lack of description.
From the tool's definition Tool name 'amocrm_tag_contact' suggests tagging/labeling a contact in AmoCRM, which is a write operation (modifying contact metadata).
Attacks that exploit this kind of access
The rule that runs amocrm_tag_contact 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_tag_contact, this is the rule to start with:
amocrm_tag_contact 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_tag_contact call is checked against it from then on.
Questions about amocrm_tag_contact
amocrm_tag_contact 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_tag_contact: 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_tag_contact 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_tag_contact 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_tag_contact. 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_tag_contact 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