Remove a tag from an entity
AI agents call remove_entity_tag to permanently remove resources in CiviCRM MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a tag from an entity deletes the association between the tag and the entity. This is a destructive action as it cannot be automatically undone; the tag-entity relationship is permanently removed. While the tag and entity themselves remain, the association is lost. Severity is medium since it affects metadata/classification rather than primary records.
From the tool's definition 'Remove a tag from an entity' — removing a tag is an irreversible deletion of the tag association
Attacks that exploit this kind of access
Remove a tag from an entity. It is categorised as a Destructive tool in the CiviCRM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CiviCRM MCP Server MCP server in PolicyLayer and add a rule for remove_entity_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 CiviCRM MCP Server. Nothing to install.
remove_entity_tag is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_entity_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 remove_entity_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.
remove_entity_tag is provided by the CiviCRM MCP Server MCP server (johncallhub/civicrm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →