List devices paired to the Google Health account (e.g. Apple Watch import source, Fitbit Air,
AI agents call list_paired_devices 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 queries and returns information about paired devices associated with the user's Google Health account. It performs a read-only operation without creating, modifying, deleting, or executing any external actions. The blast radius of misuse is minimal—an AI agent could enumerate devices but cannot change configurations, delete devices, or access device data without additional permissions.
From the tool's definition Tool name 'list_paired_devices' and description 'List devices paired to the Google Health account' indicate a retrieval/query operation with no modification or side effects.
Attacks that exploit this kind of access
List devices paired to the Google Health account (e.g. Apple Watch import source, Fitbit Air,. 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 list_paired_devices: 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.
list_paired_devices 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 list_paired_devices 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 list_paired_devices. 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.
list_paired_devices 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 →