Low Risk

get-cycle

Get a single physiological cycle by ID with strain and heart rate data

Single-target operation

Part of the Whoop MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

whoop-mcp Read

AI agents call get-cycle to retrieve information from Whoop without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get-cycle only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-ashwanthramkl-whoop-mcp.yaml
tools:
  get-cycle:
    rules:
      - action: allow

See the full Whoop policy for all 10 tools.

Tool Name get-cycle
Category Read
MCP Server Whoop MCP Server
Risk Level Low

View all 10 tools →

Agents calling read-class tools like get-cycle have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the get-cycle tool do? +

Get a single physiological cycle by ID with strain and heart rate data. It is categorised as a Read tool in the Whoop MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-cycle? +

Add a rule in your Intercept YAML policy under the tools section for get-cycle. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Whoop MCP server.

What risk level is get-cycle? +

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

Can I rate-limit get-cycle? +

Yes. Add a rate_limit block to the get-cycle rule in your Intercept 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-cycle completely? +

Set action: deny in the Intercept policy for get-cycle. 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-cycle? +

get-cycle is provided by the Whoop MCP server (whoop-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.