Health-check the Google Health connection: confirms the OAuth token works, reports granted vs
AI agents call connection_status to retrieve information from Google Health without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a status check on an existing OAuth connection, which is a non-destructive read operation. It retrieves connection metadata and permission information but does not create, modify, delete, or execute any operations. The health-check nature means it has minimal blast radius if invoked by an AI agent—it simply reports current state.
From the tool's definition Tool description indicates it "Health-check the Google Health connection: confirms the OAuth token works, reports granted vs". The verb "confirms" and "reports" are read-only operations that query connection state without modifying data.
Attacks that exploit this kind of access
Health-check the Google Health connection: confirms the OAuth token works, reports granted vs. It is categorised as a Read tool in the Google Health MCP Server, which means it retrieves data without modifying state.
Register the Google Health MCP server in PolicyLayer and add a rule for connection_status: 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 Health. Nothing to install.
connection_status 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 connection_status 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 connection_status. 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.
connection_status is provided by the Google Health MCP server (madfreakz/google-health-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 →