Get raw sleep data directly from the wellness service with full detail including heart rate and SpO2 during sleep
AI agents call get_sleep_data_raw 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 historical sleep metrics (heart rate and SpO2 data) from the user's Garmin wellness account. It performs read-only data access with no side effects, reversibility concerns, or capability to modify, delete, or trigger external operations. The blast radius of misuse is limited to unauthorized data exposure rather than system compromise or data loss.
From the tool's definition Tool name includes 'get' and description states 'Get raw sleep data directly from the wellness service' - action is retrieval/query of existing data with no modification, deletion, or external command execution.
Documented attack patterns abuse exactly the kind of access get_sleep_data_raw 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_sleep_data_raw:
{
"version": "1",
"default": "deny",
"tools": {
"get_sleep_data_raw": {}
}
}get_sleep_data_raw 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 raw sleep data directly from the wellness service with full detail including heart rate and SpO2 during sleep. 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_sleep_data_raw: 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_sleep_data_raw 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_sleep_data_raw 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_sleep_data_raw. 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_sleep_data_raw 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.