check-url-slug-exists

The

SERVERGoHighLevel MCP Server SOURCEdrausal/gohighlevel-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/drausal-gohighlevel-mcp/check-url-slug-exists.md

WHAT IT DOES

What check-url-slug-exists does on GoHighLevel MCP Server

AI agents call check-url-slug-exists 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.

RISK

Why check-url-slug-exists is rated Low

This tool appears to check whether a URL slug exists in GoHighLevel's system, which is a retrieval/query operation with no side effects. No data is created, modified, deleted, or financial transactions occur. This fits the Read category pattern of existence checks and lookups.

From the tool's definition Tool name 'check-url-slug-exists' and context of checking for existence indicates a query/lookup operation with no data modification. The description is incomplete ('The'), but the name strongly suggests a read-only verification operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check-url-slug-exists 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 check-url-slug-exists, this is the rule to start with:

check-url-slug-exists Allowed

check-url-slug-exists is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check-url-slug-exists": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GoHighLevel MCP Server, apply this rule, and every check-url-slug-exists call is checked against it from then on.

FAQ

Questions about check-url-slug-exists

What does the check-url-slug-exists tool do? +

The. 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-exists? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for check-url-slug-exists: 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-exists? +

check-url-slug-exists is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check-url-slug-exists? +

Yes. Add a rate_limit block to the check-url-slug-exists 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-exists completely? +

Set action: deny in the PolicyLayer policy for check-url-slug-exists. 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-exists? +

check-url-slug-exists 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.

KEEP EXPLORING

More on GoHighLevel MCP Server, and thousands of servers like it.

This server

All 406 GoHighLevel MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →