AI agents call list_activities to retrieve information from Garmin Workouts MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries activity data with no side effects. It is a listing/retrieval operation that does not modify, execute code, delete data, or commit financial transactions. While the description is empty, the tool name and context strongly indicate read-only functionality with minimal blast radius if misused.
From the tool's definition Tool name 'list_activities' indicates a retrieval operation. Server description mentions 'viewing activities' as a capability. The tool is grouped with other read-only tools like 'get_activity', 'get_activity_weather', 'get_calendar', and 'get_workout'.
Documented attack patterns abuse exactly the kind of access list_activities gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Garmin Workouts MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_activities:
{
"version": "1",
"default": "deny",
"tools": {
"list_activities": {}
}
}list_activities 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_activities. It is categorised as a Read tool in the Garmin Workouts MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Garmin Workouts MCP Server MCP server in PolicyLayer and add a rule for list_activities: 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 Garmin Workouts MCP Server. Nothing to install.
list_activities 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_activities 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_activities. 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_activities is provided by the Garmin Workouts MCP Server MCP server (st3v/garmin-workouts-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Garmin Workouts MCP Server, 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.
10 Garmin Workouts MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.