Delete a business reply to a review
AI agents call gbp_delete_review_reply to permanently remove resources in Google Business Profile MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a business reply, which cannot be undone. Even though the deletion is scoped to a single review reply (not the review itself), the irreversible removal of published business communications qualifies it as Destructive.
From the tool's definition Tool name contains 'delete' and description states 'Delete a business reply to a review' — this irreversibly removes content.
Attacks that exploit this kind of access
Delete a business reply to a review. It is categorised as a Destructive tool in the Google Business Profile MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Business Profile MCP Server MCP server in PolicyLayer and add a rule for gbp_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 Google Business Profile MCP Server. Nothing to install.
gbp_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.
Yes. Add a rate_limit block to the gbp_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.
Set action: deny in the PolicyLayer policy for gbp_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.
gbp_delete_review_reply is provided by the Google Business Profile MCP Server MCP server (narkov/gbp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →