Low Risk

get_floors

Get floors climbed data Args: date: Date in YYYY-MM-DD format

How to control get_floors ↓

AI agents call get_floors 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 retrieves historical fitness data (floors climbed) from Garmin Connect without creating, modifying, or deleting any information. It has no side effects and poses minimal risk—the worst outcome of misuse would be unauthorized access to personal health metrics already stored in the user's account.

From the tool's definition Tool name 'get_floors' and description 'Get floors climbed data' indicate a retrieval operation with no modification capability. The only argument is a date filter, used for querying existing data.

Documented attack patterns abuse exactly the kind of access get_floors 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_floors:

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

get_floors 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_floors tool do? +

Get floors climbed data 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_floors? +

Register the Garmin MCP Server MCP server in PolicyLayer and add a rule for get_floors: 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_floors? +

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

Can I rate-limit get_floors? +

Yes. Add a rate_limit block to the get_floors 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_floors completely? +

Set action: deny in the PolicyLayer policy for get_floors. 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_floors? +

get_floors 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.