AI agents call get_steps_and_calories to retrieve information from Garmin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical daily fitness statistics (steps, distance, calories, floors, intensity minutes) from Garmin Connect without modifying, deleting, or executing any actions. It is a straightforward data query operation with no capability to alter state or trigger external operations. The explicit 'read-only' designation of the server confirms the classification.
From the tool's definition Server description explicitly states 'read-only MCP tools' and tool retrieves 'Daily step total, distance, calories, floors, and intensity minutes' — querying health metrics with no side effects.
Attacks that exploit this kind of access
Daily step total, distance, calories, floors, and intensity minutes. It is categorised as a Read tool in the Garmin MCP Server, which means it retrieves data without modifying state.
Register the Garmin MCP server in PolicyLayer and add a rule for get_steps_and_calories: 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. Nothing to install.
get_steps_and_calories 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_steps_and_calories 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_steps_and_calories. 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_steps_and_calories is provided by the Garmin MCP server (tyler-irving/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 →