Add a tag to an entity
AI agents use add_entity_tag to create or update resources in CiviCRM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CiviCRM MCP Server environment.
Adding a tag to an entity in CiviCRM creates or modifies metadata/labels associated with a contact or other entity. This is a reversible operation (tags can be removed), making it Write category rather than Read (which retrieves without modification) or Destructive (which cannot be undone).
From the tool's definition Tool name 'add_entity_tag' and description 'Add a tag to an entity' indicate a modification operation. The sibling tools on the server include 'create_*' (Write) and 'delete_*' (Destructive) operations, positioning this as a reversible data modification.
Attacks that exploit this kind of access
Add a tag to an entity. It is categorised as a Write tool in the CiviCRM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CiviCRM MCP Server MCP server in PolicyLayer and add a rule for add_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.
add_entity_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 add_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 add_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.
add_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 →