Get weekly aggregated stress data for trend analysis. Defaults to 52 weeks (1 year). Max 52 weeks
AI agents call get_weekly_stress to retrieve information from Garmin Connect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical stress metrics from Garmin Connect without creating, modifying, or deleting any data. It is a simple data retrieval operation with no side effects, fitting the Read category. The low severity reflects minimal risk—an AI agent could only passively retrieve the user's existing stress data without causing harm.
From the tool's definition The tool 'get_weekly_stress' retrieves aggregated stress data with no modification capabilities. Keywords 'Get' and 'data for trend analysis' indicate a read-only query operation. No parameters mention modification, deletion, or side effects.
Documented attack patterns abuse exactly the kind of access get_weekly_stress 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 get_weekly_stress:
{
"version": "1",
"default": "deny",
"tools": {
"get_weekly_stress": {}
}
}get_weekly_stress 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 weekly aggregated stress data for trend analysis. Defaults to 52 weeks (1 year). Max 52 weeks. It is categorised as a Read tool in the Garmin Connect MCP Server, which means it retrieves data without modifying state.
Register the Garmin Connect MCP server in PolicyLayer and add a rule for get_weekly_stress: 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.
get_weekly_stress 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_weekly_stress 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_weekly_stress. 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_weekly_stress 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.