New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

ghl_request

A execute tool on the GoHighLevel MCP server.

SERVERGoHighLevel MCP Server SOURCEbasicmachines-co/open-ghl-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/basicmachines-co-open-ghl-mcp/ghl-request.md

What ghl_request does on GoHighLevel MCP Server

AI agents invoke ghl_request to trigger actions in GoHighLevel MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why ghl_request is rated High

The tool name 'ghl_request' suggests a generic request executor against the GoHighLevel API. With an empty description, the exact capability is unknown, but given the server context (CRM with write/delete capabilities implied by sibling tools), this could perform any API operation including destructive ones.

From the tool's definition Tool name 'ghl_request' with empty description; server manages CRM data including contacts, conversations, opportunities, calendars, and forms

Questions about ghl_request

What does the ghl_request tool do? +

ghl_request is a execute tool on the GoHighLevel MCP Server MCP server. It is categorised as a Execute tool in the GoHighLevel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ghl_request? +

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

ghl_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ghl_request? +

Yes. Add a rate_limit block to the ghl_request 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 ghl_request completely? +

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

ghl_request is provided by the GoHighLevel MCP Server MCP server (basicmachines-co/open-ghl-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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GoHighLevel MCP Server's. Pull the full record:

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.