attach_tags
Attach one or more tags to a member/account. Useful for segmenting members after filtering.
This record as markdown: /tools/io-favcrm-favcrm/attach-tags.md
What attach_tags does on FavCRM
AI agents use attach_tags 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 |
|---|---|---|---|
tagId | string | Yes | Tag ID to attach |
accountIds | array | Yes | Member/account IDs to tag (max 100) |
Parameters from the server's own tool schema.
Why attach_tags is rated Medium
This tool creates or modifies data reversibly by adding tags to CRM records. Tags can typically be removed or changed later, making it a Write operation rather than Destructive. The severity is medium because misuse could result in incorrect customer segmentation, affecting business operations and customer communications, but the changes are reversible and don't directly expose financial transactions or delete data.
From the tool's definition The tool 'attach_tags' performs the action of attaching or adding tags to members/accounts, which constitutes a modification of data.
Attacks that exploit this kind of access
The rule that runs attach_tags 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 attach_tags, this is the rule to start with:
attach_tags 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 attach_tags call is checked against it from then on.
Questions about attach_tags
Attach one or more tags to a member/account. Useful for segmenting members after filtering. 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.
attach_tags accepts 2 parameters: tagId, accountIds. Required: tagId, accountIds. 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 attach_tags: 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.
attach_tags 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 attach_tags 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 attach_tags. 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.
attach_tags 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