AI agents call audit_google_business_profile to retrieve information from Posterly without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads and audits profile data from a connected Google Business Profile location. It gathers information about completeness, categories, media, attributes, and reviews to produce recommendations. There is no indication of writing, executing, or deleting data. This is a read-only analysis operation.
From the tool's definition 'Run a live local-profile audit' and 'including completeness, categories, media, attributes, reviews, and recommendations' — purely retrieves and analyzes existing data with no modifications
Attacks that exploit this kind of access
Run a live local-profile audit for a connected Google Business Profile location, including completeness, categories, media, attributes, reviews, and recommendations. It is categorised as a Read tool in the Posterly MCP Server, which means it retrieves data without modifying state.
Register the Posterly MCP server in PolicyLayer and add a rule for audit_google_business_profile: 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 Posterly. Nothing to install.
audit_google_business_profile 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 audit_google_business_profile 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 audit_google_business_profile. 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.
audit_google_business_profile is provided by the Posterly MCP server (posterly-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 →