create_running_workout · Garmin Connect MCP: Risk & Policy

WHAT IT DOES

What create_running_workout does on Garmin Connect MCP

AI agents use create_running_workout to create or update resources in Garmin Connect MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Garmin Connect MCP environment.

WHY IT NEEDS A POLICY

Why create_running_workout needs a policy

The tool creates a new workout resource in the Garmin Connect system, which is a reversible write operation. This modifies user training data but is not destructive (can be edited or deleted), not financial, and not code execution. Severity is medium because a misused automated workout creation could flood the user's training log or create conflicting training plans, but this is easily correctable.

From the tool's definition Tool name is 'create_running_workout' indicating creation of new data/resource. Server context shows it integrates with Garmin Connect for training management. Sibling tools are predominantly read-only (get_*), making this a clear write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_running_workout Rate-limited

create_running_workout stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_running_workout": {
      "limits": [
        {
          "counter": "create_running_workout_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 Connect MCP, so you can run agents against it safely.

FAQ

Questions about create_running_workout

What does the create_running_workout tool do? +

create_running_workout. It is categorised as a Write tool in the Garmin Connect MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_running_workout? +

Register the Garmin Connect MCP server in PolicyLayer and add a rule for create_running_workout: 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 Connect MCP. Nothing to install.

What risk level is create_running_workout? +

create_running_workout is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_running_workout? +

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

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

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