Get weight measurements between specified dates
AI agents call get_weigh_ins 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 queries and retrieves historical weight measurement data within a date range. It performs no side effects, does not modify data, and does not execute external operations. The action is purely informational retrieval, fitting the Read category. Severity is low because exposure of personal weight data has limited immediate impact compared to financial or destructive operations, though privacy concerns exist.
From the tool's definition Tool name 'get_weigh_ins' and description 'Get weight measurements between specified dates' indicate data retrieval with no modification or deletion of records.
Attacks that exploit this kind of access
Get weight measurements between specified dates. 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_weigh_ins: 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_weigh_ins 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_weigh_ins 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_weigh_ins. 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_weigh_ins 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 →