tp_update_speed_zones · TrainingPeaks- MCP: Risk & Policy

WHAT IT DOES

What tp_update_speed_zones does on TrainingPeaks-MCP

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

WHY IT NEEDS A POLICY

Why tp_update_speed_zones needs a policy

This tool modifies user training data (pace zones for running/swimming) but does not delete, destroy, or execute arbitrary operations. Changes to pace zones are reversible and do not trigger external systems or financial transactions. The blast radius is moderate: incorrect pace zones could degrade training guidance quality, but the action is non-destructive and the user can correct it.

From the tool's definition Tool name 'tp_update_speed_zones' and description 'Update run/swim pace zones' indicate modification of existing training configuration data. The verb 'Update' signifies reversible alteration of pace zone settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tp_update_speed_zones Rate-limited

tp_update_speed_zones 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": {
    "tp_update_speed_zones": {
      "limits": [
        {
          "counter": "tp_update_speed_zones_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 TrainingPeaks-MCP, so you can run agents against it safely.

FAQ

Questions about tp_update_speed_zones

What does the tp_update_speed_zones tool do? +

Update run/swim pace zones. It is categorised as a Write tool in the TrainingPeaks-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 tp_update_speed_zones? +

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

What risk level is tp_update_speed_zones? +

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

Can I rate-limit tp_update_speed_zones? +

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

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

tp_update_speed_zones is provided by the TrainingPeaks- MCP server (jamsusmaximus/trainingpeaks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.