Get equipment/gear used in an activity.
AI agents call get_activity_gear to retrieve information from Mcp Garmin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical equipment/gear information from Garmin Connect without creating, modifying, or deleting data. It is a simple query operation that returns metadata about what gear was used in a completed activity. No side effects or state changes occur. Consistent with other sibling tools (get_activities, get_body_composition, etc.) all classified as read operations.
From the tool's definition Tool is part of a 'read-only access' MCP server; function name 'get_activity_gear' uses 'get' verb; retrieves equipment/gear data associated with an activity with no modification capability.
Attacks that exploit this kind of access
Get equipment/gear used in an activity. It is categorised as a Read tool in the Mcp Garmin MCP Server, which means it retrieves data without modifying state.
Register the Mcp Garmin 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 Mcp Garmin. 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 Mcp Garmin MCP server (obrien-matthew/mcp-garmin). 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 →