AI agents call export_activity to retrieve information from Garmin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and exports an existing activity in a specified file format. It reads data from Garmin Connect and produces a file output — no data is created, modified, or deleted. The blast radius is low since it only exposes a single activity's data.
From the tool's definition Export a single activity file. fmt options: gpx, tcx, fit, csv.
Attacks that exploit this kind of access
Export a single activity file. fmt options: gpx, tcx, fit, csv. It is categorised as a Read tool in the Garmin MCP Server, which means it retrieves data without modifying state.
Register the Garmin MCP server in PolicyLayer and add a rule for export_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. Nothing to install.
export_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 export_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 export_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.
export_activity is provided by the Garmin MCP server (marcelohensantos/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 →