Add hydration data
AI agents use add_hydration_data to create or update resources in Garmin MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Garmin MCP Server environment.
This tool adds health/fitness data to a user's Garmin Connect account. While the operation is reversible (data can be edited or deleted later), it modifies persistent user health records. The primary risk is inaccurate or false health data being recorded, which could mislead the user or health professionals relying on this data, but does not involve code execution, irreversible deletion, or financial transactions.
From the tool's definition Tool name 'add_hydration_data' and description 'Add hydration data' indicate the tool creates or modifies hydration records in Garmin Connect, a reversible operation typical of Write category tools.
Attacks that exploit this kind of access
Add hydration data. It is categorised as a Write tool in the Garmin MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Garmin MCP Server MCP server in PolicyLayer and add a rule for add_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.
add_hydration_data is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_hydration_data is provided by the Garmin MCP Server MCP server (shubhaankar-sharma/garmin-mcp-railway). 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 →