Create a manual activity entry. Use get_activity_types to find valid activityTypeKey values
AI agents use create_manual_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 a new activity record in the user's Garmin Connect account. This is a reversible write operation (the activity can be deleted via delete_activity), with no financial impact, code execution, or destructive effects. The blast radius is limited to creating a single user-controlled data entry in their own fitness tracking account.
From the tool's definition Tool name includes 'create' and description states 'Create a manual activity entry', indicating data creation operation.
Documented attack patterns abuse exactly the kind of access create_manual_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 create_manual_activity:
{
"version": "1",
"default": "deny",
"tools": {
"create_manual_activity": {
"limits": [
{
"counter": "create_manual_activity_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_manual_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.
Create a manual activity entry. Use get_activity_types to find valid activityTypeKey values. 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 create_manual_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.
create_manual_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 create_manual_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 create_manual_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.
create_manual_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.