Update an existing GBP post
AI agents use gbp_update_post to create or update resources in Google Business Profile MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Business Profile MCP Server environment.
This tool modifies existing posts on a Google Business Profile, which is a reversible write operation. It does not delete data (which would be Destructive) or execute arbitrary code (which would be Execute). The severity is medium because unauthorized post modifications could damage business reputation and customer trust, but the effects can be reversed by further edits or deletions.
From the tool's definition Tool name 'gbp_update_post' and description 'Update an existing GBP post' clearly indicate modification of existing data.
Attacks that exploit this kind of access
Update an existing GBP post. It is categorised as a Write tool in the Google Business Profile MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Business Profile MCP Server MCP server in PolicyLayer and add a rule for gbp_update_post: 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_update_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gbp_update_post 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_update_post. 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_update_post 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 →