update_tag

Rename or recolor an existing CRM tag.

SERVERFavCRM SOURCEhttps://api.favcrm.io/mcp
Medium RISK CLASS
Category Write
Parameters 31 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

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

Questions about update_tag

What does the update_tag tool do? +

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.

What parameters does update_tag accept? +

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.

How do I enforce a policy on update_tag? +

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.

What risk level is update_tag? +

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

Can I rate-limit update_tag? +

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.

How do I block update_tag completely? +

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.

What MCP server provides update_tag? +

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.

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