check_url_slug

Check if a URL slug is available for use. Use this before creating or updating blog posts to ensure unique URLs.

Server GoHighLevel MCP Server keshigami/ghl-mcp-workiong
Category Read
Risk class Low
Parameters 00 required

What check_url_slug does on GoHighLevel MCP Server

AI agents call check_url_slug to retrieve information from GoHighLevel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why check_url_slug needs a policy

This is a query/lookup operation that retrieves information about URL slug availability. It has no side effects—it does not create, modify, delete, or execute code. It simply validates whether a slug is in use before a subsequent action. This is a classic Read category operation with low severity as misuse would at worst provide false information about availability.

From the tool's definition The tool 'check_url_slug' is described as checking if a URL slug is available for use. The verb 'check' and the purpose of validation/availability checking indicate this is a read operation that queries existing data without modifying it.

Questions about check_url_slug

What does the check_url_slug tool do? +

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 GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_url_slug? +

Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. Nothing to install.

What risk level is check_url_slug? +

check_url_slug is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_url_slug? +

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.

How do I block check_url_slug completely? +

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.

What MCP server provides check_url_slug? +

check_url_slug is provided by the GoHighLevel MCP Server MCP server (keshigami/ghl-mcp-workiong). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.