custom_garmin_request · Garmin MCP Server MCP: Risk & Policy

WHAT IT DOES

What custom_garmin_request does on Garmin MCP Server

AI agents invoke custom_garmin_request to trigger actions in Garmin MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why custom_garmin_request needs a policy

This tool allows making arbitrary/custom API requests to Garmin Connect, which could include reads, writes, or destructive operations depending on what the user specifies. Since it permits execution of arbitrary operations against an external service, it falls under Execute. The blast radius is high because a misused tool could trigger any supported Garmin Connect API action, including data modification or deletion.

From the tool's definition 'Make custom API requests to Garmin Connect (advanced users)' — arbitrary API request execution against external service

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

custom_garmin_request Rate-limited

custom_garmin_request stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "custom_garmin_request": {
      "limits": [
        {
          "counter": "custom_garmin_request_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Garmin MCP Server, so you can run agents against it safely.

FAQ

Questions about custom_garmin_request

What does the custom_garmin_request tool do? +

Make custom API requests to Garmin Connect (advanced users). It is categorised as a Execute tool in the Garmin MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on custom_garmin_request? +

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

custom_garmin_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit custom_garmin_request? +

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

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

custom_garmin_request is provided by the Garmin MCP Server MCP server (j4sun/garmin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.