get-tags-by-ids
A read tool on the GoHighLevel MCP server.
This record as markdown: /tools/drausal-gohighlevel-mcp/get-tags-by-ids.md
What get-tags-by-ids does on GoHighLevel MCP Server
AI agents call get-tags-by-ids to retrieve information from GoHighLevel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get-tags-by-ids is rated Low
This tool retrieves tag information based on provided IDs. It has no side effects—it does not create, modify, delete, or execute any operations. It is a straightforward data retrieval function consistent with Read category classification. Blast radius is minimal since misuse would only expose existing tag metadata.
From the tool's definition Tool name 'get-tags-by-ids' and description 'Get tags by ids' indicate a retrieval operation. The verb 'get' combined with 'by ids' is a standard read pattern that queries existing data without modification.
Attacks that exploit this kind of access
The rule that runs get-tags-by-ids safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get-tags-by-ids, this is the rule to start with:
get-tags-by-ids is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GoHighLevel MCP Server, apply this rule, and every get-tags-by-ids call is checked against it from then on.
Questions about get-tags-by-ids
get-tags-by-ids is a read tool on the GoHighLevel MCP Server MCP server. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for get-tags-by-ids: 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 GoHighLevel MCP Server. Nothing to install.
get-tags-by-ids 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-tags-by-ids 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-tags-by-ids. 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-tags-by-ids is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoHighLevel MCP Server, and thousands of servers like it.
This server
Across the catalogue