This record as markdown: /tools/io-favcrm-favcrm/update-tag.md
What update_tag does on FavCRM
AI agents use update_tag to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | New tag name |
color | object | — | New color, or null to clear |
tagId | string | Yes | The tag ID to update |
Parameters from the server's own tool schema.
Why update_tag is rated Medium
This tool modifies existing tag metadata (name and color) within the CRM system. These changes are reversible — tags can be renamed again or recolored to different values. While this affects data organization in a CRM serving service businesses, the impact is limited to tag metadata and does not constitute destructive action, financial risk, or code execution.
From the tool's definition Tool description states 'Rename or recolor an existing CRM tag' — these are modification operations that change tag properties reversibly. The verb 'update' combined with 'rename' and 'recolor' indicates data modification without deletion.
Attacks that exploit this kind of access
The rule that runs update_tag safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_tag, this is the rule to start with:
update_tag 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 FavCRM, apply this rule, and every update_tag call is checked against it from then on.
Questions about update_tag
Rename or recolor an existing CRM tag. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_tag accepts 3 parameters: name, color, tagId. Required: tagId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for update_tag: 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 FavCRM. Nothing to install.
update_tag 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 update_tag 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 update_tag. 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.
update_tag is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue