AI agents use set_activity_name 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 modifies activity data (renaming) in a reversible manner. It creates or updates existing records without deleting or destroying data, making it a Write operation. The severity is medium because renaming activities has limited blast radius—it affects only metadata and can be undone by renaming again, but could cause confusion if an agent systematically renames many activities without user intent.
From the tool's definition Tool name is 'set_activity_name' and description states 'Rename an activity', indicating modification of existing activity metadata.
Documented attack patterns abuse exactly the kind of access set_activity_name 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 set_activity_name:
{
"version": "1",
"default": "deny",
"tools": {
"set_activity_name": {
"limits": [
{
"counter": "set_activity_name_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_activity_name 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.
Rename 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 set_activity_name: 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.
set_activity_name 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 set_activity_name 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 set_activity_name. 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.
set_activity_name 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.