create_tag
Create a CRM tag for customer segmentation and organization.
This record as markdown: /tools/io-favcrm-favcrm/create-tag.md
What create_tag does on FavCRM
AI agents use create_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 | Yes | Tag name |
color | string | — | Optional display color, e.g. #2563eb |
Parameters from the server's own tool schema.
Why create_tag is rated Medium
The tool creates a new CRM tag, which is a reversible Write operation. Tags are metadata for customer organization and segmentation—creating one does not execute code, delete data irreversibly, move money, or trigger external actions with unpredictable side effects. The impact is limited to adding a classification label in the CRM, making it low severity.
From the tool's definition create_tag - creates a new tag for customer segmentation and organization. This is a Create operation that adds a new data entity to the CRM system.
Attacks that exploit this kind of access
The rule that runs create_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 create_tag, this is the rule to start with:
create_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 create_tag call is checked against it from then on.
Questions about create_tag
Create a CRM tag for customer segmentation and organization. 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.
create_tag accepts 2 parameters: name, color. Required: name. 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 create_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.
create_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 create_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 create_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.
create_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