Get respiratory rate data for a given date.
AI agents call get_respiration_data to retrieve information from Mcp Garmin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical respiratory rate data without any side effects. It is a query operation that fetches existing metrics from Garmin Connect. The server is explicitly read-only, and the tool name and description contain only retrieval semantics ('Get'). Misuse by an AI agent would be limited to potential privacy concerns around viewing sensitive health data, not operational damage, making severity low.
From the tool's definition Tool description states 'Get respiratory rate data' with no modification capability; server description explicitly states 'read-only access to daily health metrics'; all sibling tools follow read-only pattern (get_activities, get_body_battery, etc.)
Attacks that exploit this kind of access
Get respiratory rate data for a given date. It is categorised as a Read tool in the Mcp Garmin MCP Server, which means it retrieves data without modifying state.
Register the Mcp Garmin MCP server in PolicyLayer and add a rule for get_respiration_data: 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 Mcp Garmin. Nothing to install.
get_respiration_data 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 get_respiration_data 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 get_respiration_data. 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.
get_respiration_data is provided by the Mcp Garmin MCP server (obrien-matthew/mcp-garmin). 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 →