delete_review_reply

Delete a review reply

SERVERGoHighLevel MCP Server SOURCEbusybee3333/go-high-level-mcp-2026-complete
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/busybee3333-go-high-level-mcp-2026-complete/delete-review-reply.md

What delete_review_reply does on GoHighLevel MCP Server

AI agents call delete_review_reply to permanently remove resources in GoHighLevel MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_review_reply is rated Critical

The delete_review_reply tool performs an irreversible deletion operation on review replies. This falls squarely into the Destructive category because deletion cannot be undone and permanently removes content. In a CRM context with 461 tools managing customer interactions and reputation, erasing review replies could damage business relationships and customer records.

From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a review reply' — this irreversibly removes data that cannot be recovered.

Questions about delete_review_reply

What does the delete_review_reply tool do? +

Delete a review reply. It is categorised as a Destructive tool in the GoHighLevel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_review_reply? +

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

delete_review_reply is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_review_reply? +

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

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

delete_review_reply 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.

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.