check_url_slug
Check if a URL slug is available for use. Use this before creating or updating blog posts to ensure unique URLs.
This record as markdown: /tools/ghl/check-url-slug.md
What check_url_slug does on Ghl
AI agents call check_url_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 |
|---|---|---|---|
postId | string | — | Optional post ID when updating an existing post (to exclude itself from the check) |
urlSlug | string | Yes | URL slug to check for availability |
Parameters from the server's own tool schema.
Why check_url_slug is rated Low
This is a lookup/validation tool that queries whether a resource exists or is available. It performs no modifications, deletions, or external executions. The severity is low because misuse would at worst provide incorrect availability information, with minimal blast radius.
From the tool's definition Tool checks if a URL slug is available; it 'retrieves or queries data' to determine availability without making any changes. The description explicitly states it is used 'before creating or updating' (i.e., a pre-check action), not the creation/update itself.
Attacks that exploit this kind of access
The rule that runs check_url_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 check_url_slug, this is the rule to start with:
check_url_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 check_url_slug call is checked against it from then on.
Questions about check_url_slug
Check if a URL slug is available for use. Use this before creating or updating blog posts to ensure unique URLs. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
check_url_slug accepts 2 parameters: postId, urlSlug. Required: urlSlug. 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 check_url_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.
check_url_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 check_url_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 check_url_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.
check_url_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