get_stress_data
AI agents call get_stress_data 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.
This tool retrieves stress data from Garmin Connect, consistent with the server's stated purpose of enabling 'training analysis' and 'recovery checks' based on real metrics. The 'get_' verb pattern and alignment with sibling read-only tools confirm this is a data query operation with no destructive, financial, or execution capabilities.
From the tool's definition Tool name 'get_stress_data' uses the 'get_' prefix indicating data retrieval with no modification. All sibling tools on this server (get_activities, get_activity_zones, get_bike_session, get_fitness, etc.) are Read operations that query Garmin Connect metrics.
Attacks that exploit this kind of access
get_stress_data. 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_stress_data: 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_stress_data 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_stress_data 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_stress_data. 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_stress_data 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 →