Get gear data used for an activity
AI agents call get_activity_gear to retrieve information from Garmin 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 historical gear information associated with a specific activity. It performs a query-like operation (get) without side effects. The data returned is fitness metadata (equipment used) that is already stored in Garmin Connect. No data is created, modified, deleted, or executed. This is consistent with other read-only tools on the server like get_activity, get_activities_by_date, etc.
From the tool's definition Tool name 'get_activity_gear' and description 'Get gear data used for an activity' indicate a retrieval operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get gear data used for an activity. It is categorised as a Read tool in the Garmin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Garmin MCP Server MCP server in PolicyLayer and add a rule for get_activity_gear: 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 MCP Server. Nothing to install.
get_activity_gear 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_gear 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_gear. 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_gear is provided by the Garmin MCP Server MCP server (jbaker48/garmin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →