Get daily respiration rate data throughout the day. Single date; for ranges use get_respiration_range
AI agents call get_respiration to retrieve information from Garmin Connect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves health metrics (respiration rate) without side effects. It is a pure read operation that queries existing data from Garmin Connect. No data is created, modified, deleted, or used to trigger external operations. The blast radius of misuse is minimal—an AI agent could only over-query or access data it shouldn't see, not cause harm through the tool itself.
From the tool's definition Tool name and description indicate retrieval only: 'Get daily respiration rate data' with no mention of modification, deletion, or execution. The description specifies querying a single date's metric data.
Documented attack patterns abuse exactly the kind of access get_respiration gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Garmin Connect, and nothing reaches the server without passing your rules. This is the rule we recommend for get_respiration:
{
"version": "1",
"default": "deny",
"tools": {
"get_respiration": {}
}
}get_respiration is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get daily respiration rate data throughout the day. Single date; for ranges use get_respiration_range. It is categorised as a Read tool in the Garmin Connect MCP Server, which means it retrieves data without modifying state.
Register the Garmin Connect MCP server in PolicyLayer and add a rule for get_respiration: 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 Garmin Connect. Nothing to install.
get_respiration 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 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. 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 is provided by the Garmin Connect MCP server (nicolasvegam/garmin-connect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 97 Garmin Connect tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
97 Garmin Connect tools catalogued and risk-classified — across an index of 42,500+ MCP servers.