List local posts for a GBP location
AI agents call gbp_list_posts to retrieve information from Google Business Profile MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing posts from a Google Business Profile location. It has no side effects—it does not create, modify, delete, or execute operations. Listing is a read operation with minimal security impact, typically used for discovery and information retrieval. The blast radius of misuse is low since the worst outcome would be information disclosure of already-public business profile posts.
From the tool's definition Tool name 'list_posts' and description 'List local posts for a GBP location' indicate a query operation that retrieves data without modifying or deleting anything.
Attacks that exploit this kind of access
List local posts for a GBP location. It is categorised as a Read tool in the Google Business Profile MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Business Profile MCP Server MCP server in PolicyLayer and add a rule for gbp_list_posts: 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_list_posts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gbp_list_posts 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_list_posts. 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_list_posts 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 →