Get hydration data
AI agents call get_hydration_data to retrieve information from Garmin MCP Server for Poke without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing hydration data without modifying, deleting, or executing external operations. It falls squarely into the Read category as a data retrieval operation. The severity is low because unauthorized reading of hydration metrics, while a privacy concern, poses minimal immediate operational risk compared to data modification or financial tools.
From the tool's definition The tool name 'get_hydration_data' and description explicitly indicate a retrieval operation. The verb 'get' and context of reading health metrics from Garmin Connect demonstrate this is a query-only function with no side effects.
Attacks that exploit this kind of access
Get hydration data. It is categorised as a Read tool in the Garmin MCP Server for Poke MCP Server, which means it retrieves data without modifying state.
Register the Garmin MCP Server for Poke 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 for Poke. 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 for Poke MCP server (theol0403/garmin-mcp-poke). 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 →