Retrieve entity tag relationships from CiviCRM
AI agents call get_entity_tags to retrieve information from CiviCRM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries tag relationship data from CiviCRM with no side effects. It matches the 'Read' category definition: retrieves data without making any changes to the system. The blast radius of misuse is minimal—an agent could query tags but cannot modify, delete, or execute operations.
From the tool's definition Tool name 'get_entity_tags' and description 'Retrieve entity tag relationships from CiviCRM' both indicate a read-only operation that queries existing data without modification.
Attacks that exploit this kind of access
Retrieve entity tag relationships from CiviCRM. It is categorised as a Read tool in the CiviCRM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CiviCRM MCP Server MCP server in PolicyLayer and add a rule for get_entity_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 CiviCRM MCP Server. Nothing to install.
get_entity_tags is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_entity_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 get_entity_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.
get_entity_tags 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 →