Get all available activity types (running, cycling, swimming, etc.)
AI agents call get_activity_types to retrieve information from Garmin Connect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of available activity types from Garmin Connect. It does not modify, create, delete, or execute any operations—it simply retrieves reference data that exists independently of the query. This is a classic read operation with minimal risk, as accessing activity type enumerations cannot harm data integrity or trigger unintended side effects.
From the tool's definition Tool name 'get_activity_types' and description 'Get all available activity types' indicate a retrieval operation with no side effects. The verb 'Get' and the enumeration of static reference data (activity type categories) confirm read-only behavior.
Documented attack patterns abuse exactly the kind of access get_activity_types gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Garmin Connect, and nothing reaches the server without passing your rules. This is the rule we recommend for get_activity_types:
{
"version": "1",
"default": "deny",
"tools": {
"get_activity_types": {}
}
}get_activity_types 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 all available activity types (running, cycling, swimming, etc.). It is categorised as a Read tool in the Garmin Connect MCP Server, which means it retrieves data without modifying state.
Register the Garmin Connect MCP server in PolicyLayer and add a rule for get_activity_types: 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 Connect. Nothing to install.
get_activity_types 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_types 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_types. 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_types is provided by the Garmin Connect MCP server (nicolasvegam/garmin-connect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 97 Garmin Connect tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
97 Garmin Connect tools catalogued and risk-classified — across an index of 42,500+ MCP servers.