Get splits for an activity Args: activity_id: ID of the activity to retrieve splits for
AI agents call get_activity_splits to retrieve information from Garmin MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves fitness activity split data (e.g., pace/time segments) from Garmin Connect without modifying, executing external operations, or deleting anything. It is a straightforward read operation with minimal blast radius if misused — an AI agent could only retrieve splits for activities it has access to, causing no harm beyond potential data disclosure of the user's own fitness data.
From the tool's definition Tool name is 'get_activity_splits' and description states 'Get splits for an activity' — uses the verb 'get' which is a retrieval operation. Accepts only an activity_id parameter for querying, with no modification or deletion capability.
Documented attack patterns abuse exactly the kind of access get_activity_splits gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Garmin MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_activity_splits:
{
"version": "1",
"default": "deny",
"tools": {
"get_activity_splits": {}
}
}get_activity_splits is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get splits for an activity Args: activity_id: ID of the activity to retrieve splits for. It is categorised as a Read tool in the Garmin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Garmin MCP Server MCP server in PolicyLayer and add a rule for get_activity_splits: 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 MCP Server. Nothing to install.
get_activity_splits 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_splits 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_splits. 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_splits is provided by the Garmin MCP Server MCP server (taxuspt/garmin_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 126 Garmin MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
126 Garmin MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.