detach_tags
Detach one tag from one or more member/account records.
This record as markdown: /tools/io-favcrm-favcrm/detach-tags.md
What detach_tags does on FavCRM
AI agents use detach_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 detach |
accountIds | array | Yes | Member/account IDs to untag (max 100) |
Parameters from the server's own tool schema.
Why detach_tags is rated Medium
This tool modifies existing records by removing tag associations, which is a write operation. It is reversible (tags can be re-attached), so it does not qualify as Destructive. The moderate severity reflects that detaching tags from multiple records could disrupt data organization, customer segmentation, or business logic that depends on those tags, but the operation itself is non-destructive and can be undone.
From the tool's definition Tool description states 'Detach one tag from one or more member/account records' — this modifies data by removing tag associations from records, a reversible write operation.
Attacks that exploit this kind of access
The rule that runs detach_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 detach_tags, this is the rule to start with:
detach_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 detach_tags call is checked against it from then on.
Questions about detach_tags
Detach one tag from one or more member/account records. 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.
detach_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 detach_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.
detach_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 detach_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 detach_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.
detach_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