get_running_dynamics
AI agents call get_running_dynamics to retrieve information from Claude Garmin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and alignment with other querying tools on the same server indicate this retrieves running dynamics metrics (likely cadence, ground contact time, vertical oscillation, or similar) from Garmin Connect. No modification, deletion, or execution is implied. Blast radius is low since reading personal fitness data poses minimal risk.
From the tool's definition Tool name 'get_running_dynamics' begins with 'get_', indicating a retrieval operation. All sibling tools on this server (get_activities, get_fitness, get_full_snapshot, etc.) are Read-category tools that query Garmin Connect data without modification.
Attacks that exploit this kind of access
get_running_dynamics. It is categorised as a Read tool in the Claude Garmin MCP Server, which means it retrieves data without modifying state.
Register the Claude Garmin MCP server in PolicyLayer and add a rule for get_running_dynamics: 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 Claude Garmin. Nothing to install.
get_running_dynamics 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_running_dynamics 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_running_dynamics. 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_running_dynamics is provided by the Claude Garmin MCP server (jack-abyss/claude-garmin). 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 →