Get details of a specific activity by its ID. An activity represents a completed run, ride, swim, etc.
AI agents call get_activity 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 and queries data about a completed activity without any ability to modify, execute operations, or cause irreversible changes. It is a straightforward read operation.
From the tool's definition Tool name 'get_activity' and description 'Get details of a specific activity by its ID' indicate a retrieval operation with no side effects. Activities are completed workouts, and retrieving their details has no capacity to modify or delete data.
Documented attack patterns abuse exactly the kind of access get_activity 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 get_activity:
{
"version": "1",
"default": "deny",
"tools": {
"get_activity": {}
}
}get_activity 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.
Get details of a specific activity by its ID. An activity represents a completed run, ride, swim, etc. 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 get_activity: 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.
get_activity 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 get_activity 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 get_activity. 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.
get_activity 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.