// MCP TOOL REFERENCE

COROS WORKOUT TOOLS

6 tools from the Coros Workout MCP Server, categorised by risk level.

// ALL 6 COROS WORKOUT TOOLS

READ 3 tools

Read check_coros_auth Check if COROS authentication is available (from stored token or env vars). Read list_workouts List workouts from COROS Training Hub. Read search_exercises Search the COROS exercise catalog (~383 strength exercises). Filter by name, muscle group, body part, and/o...

WRITE 2 tools

Write create_workout Create a strength workout on COROS Training Hub. Resolves exercise names from the catalog, builds the full ... Write update_exercises Fetch the latest exercise catalog from COROS APIs and rebuild the local catalog. Requires authentication. F...

EXECUTE 1 tools

Execute authenticate_coros Log in to COROS Training Hub. Stores auth token for subsequent calls. Also checks COROS_EMAIL/COROS_PASSWOR...

// FAQ

How many tools does the Coros Workout MCP server have? +

The Coros Workout MCP server exposes 6 tools across 3 categories: Read, Write, Execute.

How do I enforce policies on Coros Workout tools? +

Route the Coros Workout server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Coros Workout tools fall into? +

Coros Workout tools are categorised as Read (3), Write (2), Execute (1). Each category has a recommended default policy.

Enforce policy on every Coros Workout tool call.

Start from Coros Workout, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.