Get hydration data
AI agents call get_hydration_data to retrieve information from Garmin MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves hydration metrics from Garmin Connect without modifying, deleting, or executing any operations. It is a simple data query with no destructive or reversible write effects. The 'get_' prefix is a strong indicator of read-only behavior. Severity is low because exposure of personal health data, while sensitive, does not enable financial harm, system compromise, or irreversible actions.
From the tool's definition Tool name 'get_hydration_data' and description 'Get hydration data' indicate a retrieval operation with no side effects. Consistent with sibling tools like 'get_activities_by_date', 'get_activity', which are plainly read operations.
Attacks that exploit this kind of access
Get hydration data. It is categorised as a Read tool in the Garmin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Garmin MCP Server MCP server in PolicyLayer and add a rule for get_hydration_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 Garmin MCP Server. Nothing to install.
get_hydration_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_hydration_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_hydration_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_hydration_data is provided by the Garmin MCP Server MCP server (jbaker48/garmin-mcp). 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 →