AI agents call list_workouts to retrieve information from Coros Workout without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing workout data from the COROS Training Hub without modifying, deleting, or executing any operations. It is a read-only operation that presents no risk of unintended data modification or destructive actions. Severity is low because listing workouts exposes only user's own fitness data with minimal blast radius.
From the tool's definition Tool name 'list_workouts' and description 'List workouts from COROS Training Hub' indicate data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access list_workouts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Coros Workout, and nothing reaches the server without passing your rules. This is the rule we recommend for list_workouts:
{
"version": "1",
"default": "deny",
"tools": {
"list_workouts": {}
}
}list_workouts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List workouts from COROS Training Hub. It is categorised as a Read tool in the Coros Workout MCP Server, which means it retrieves data without modifying state.
Register the Coros Workout MCP server in PolicyLayer and add a rule for list_workouts: 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 Coros Workout. Nothing to install.
list_workouts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_workouts 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.
Set action: deny in the PolicyLayer policy for list_workouts. 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.
list_workouts is provided by the Coros Workout MCP server (rowlando/coros-workout-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Coros Workout, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Coros Workout tools catalogued and risk-classified — across an index of 43,000+ MCP servers.