This record as markdown: /tools/ghl/validate-group-slug.md
What validate_group_slug does on Ghl
AI agents call validate_group_slug to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | Slug to validate |
locationId | string | — | Location ID |
Parameters from the server's own tool schema.
Why validate_group_slug is rated Low
The tool performs a validation check, which is fundamentally a read operation that queries the state of a resource (whether a slug is available) without creating, modifying, deleting, or executing side effects. It has minimal blast radius if misused.
From the tool's definition Tool description states 'Validate if a calendar group slug is available' — this is a query/check operation that retrieves availability status without modifying data.
Attacks that exploit this kind of access
The rule that runs validate_group_slug safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For validate_group_slug, this is the rule to start with:
validate_group_slug 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 Ghl, apply this rule, and every validate_group_slug call is checked against it from then on.
Questions about validate_group_slug
Validate if a calendar group slug is available. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
validate_group_slug accepts 2 parameters: slug, locationId. Required: slug. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for validate_group_slug: 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 Ghl. Nothing to install.
validate_group_slug 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 validate_group_slug 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 validate_group_slug. 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.
validate_group_slug is provided by the Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue