Link a gear item (shoes, bike) to an activity
AI agents use add_gear_to_activity to create or update resources in Garmin Connect — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Garmin Connect environment.
This tool creates or modifies data reversibly by establishing a gear-to-activity link. It is not a read operation (it changes state), not destructive (the link can be removed or changed), not execute/financial/other. Classification as Write is appropriate given it creates a new association in the fitness tracking database.
From the tool's definition Tool performs 'Link a gear item (shoes, bike) to an activity' — this modifies activity metadata by adding an association to gear, creating a new relationship that did not previously exist.
Documented attack patterns abuse exactly the kind of access add_gear_to_activity 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 add_gear_to_activity:
{
"version": "1",
"default": "deny",
"tools": {
"add_gear_to_activity": {
"limits": [
{
"counter": "add_gear_to_activity_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_gear_to_activity stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Link a gear item (shoes, bike) to an activity. It is categorised as a Write tool in the Garmin Connect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Garmin Connect MCP server in PolicyLayer and add a rule for add_gear_to_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 Connect. Nothing to install.
add_gear_to_activity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_gear_to_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 add_gear_to_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.
add_gear_to_activity 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.