Low Risk

get_stats

Get daily activity stats with curated essential metrics Returns a summary of daily health and activity data including steps, calories, heart rate, stress, body battery, and sleep metrics. Args: date: Date in YYYY-MM-DD format

How to control get_stats ↓

AI agents call get_stats 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.

Low Risk

This tool queries and retrieves existing fitness metrics (steps, calories, heart rate, stress, body battery, sleep) for a specified date. It performs no writes, deletions, or external operations. The blast radius of misuse is minimal—an AI agent could only read personal health data, which is already exposed to the MCP server connection. This is a straightforward read operation.

From the tool's definition Tool description states it 'Returns a summary of daily health and activity data' with no modification capabilities. The verb 'Get' and action 'Returns' indicate data retrieval only. No parameters enable modifications, deletions, or side effects.

Documented attack patterns abuse exactly the kind of access get_stats gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Garmin MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_stats:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_stats": {}
  }
}

get_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Garmin MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_stats tool do? +

Get daily activity stats with curated essential metrics Returns a summary of daily health and activity data including steps, calories, heart rate, stress, body battery, and sleep metrics. Args: date: Date in YYYY-MM-DD format. It is categorised as a Read tool in the Garmin MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_stats? +

Register the Garmin MCP Server MCP server in PolicyLayer and add a rule for get_stats: 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.

What risk level is get_stats? +

get_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_stats? +

Yes. Add a rate_limit block to the get_stats 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.

How do I block get_stats completely? +

Set action: deny in the PolicyLayer policy for get_stats. 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.

What MCP server provides get_stats? +

get_stats is provided by the Garmin MCP Server MCP server (taxuspt/garmin_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Garmin MCP Server tool call.

Deterministic rules across all 126 Garmin MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

126 Garmin MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.