strava_authenticate · Health MCP Server MCP: Risk & Policy

WHAT IT DOES

What strava_authenticate does on Health MCP Server

AI agents invoke strava_authenticate to trigger actions in Health 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 strava_authenticate needs a policy

This tool triggers an external browser action (opening a browser window) and initiates an OAuth authentication flow, which is an external operation with side effects beyond mere data retrieval. It falls under Execute because it runs a browser action and triggers an external authorization process, not simply reading or writing data.

From the tool's definition Opens a browser window for OAuth login to authorize access to your activity data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

strava_authenticate Rate-limited

strava_authenticate 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": {
    "strava_authenticate": {
      "limits": [
        {
          "counter": "strava_authenticate_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 Health MCP Server, so you can run agents against it safely.

FAQ

Questions about strava_authenticate

What does the strava_authenticate tool do? +

Authenticate with Strava. Opens a browser window for OAuth login to authorize access to your activity data. It is categorised as a Execute tool in the Health 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 strava_authenticate? +

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

What risk level is strava_authenticate? +

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

Can I rate-limit strava_authenticate? +

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

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

strava_authenticate is provided by the Health MCP Server MCP server (marholoubek/health_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.