Low Risk

get_review_requests

Get sent review requests

How to control get_review_requests ↓

AI agents call get_review_requests 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.

Low Risk

This tool retrieves or queries review requests that have been sent—a read-only operation with no side effects. It does not create, modify, delete, execute commands, or process financial transactions. The blast radius of misuse is minimal, as an agent could only view review request data it has access to, with no ability to alter state or trigger external actions.

From the tool's definition Tool name 'get_review_requests' and description 'Get sent review requests' indicate retrieval of existing data without modification.

Documented attack patterns abuse exactly the kind of access get_review_requests gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_review_requests:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_review_requests": {}
  }
}

get_review_requests is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register GoHighLevel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_review_requests tool do? +

Get sent review requests. 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 get_review_requests? +

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

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

Can I rate-limit get_review_requests? +

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

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

get_review_requests is provided by the GoHighLevel MCP Server MCP server (busybee3333/go-high-level-mcp-2026-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GoHighLevel MCP Server tool call.

Deterministic rules across all 566 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

566 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.