Get lactate threshold data. Critical for Norwegian double threshold
AI agents call get_lactate_threshold to retrieve information from Garmin Connect MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves lactate threshold biometric data from Garmin Connect, a passive read operation with no side effects on user data or external systems. It does not create, modify, delete, or execute any actions. Misuse would only expose personal health metrics, presenting minimal risk. Classified as Read/low severity.
From the tool's definition Tool name is 'get_lactate_threshold' and description states 'Get lactate threshold data', indicating retrieval of existing health metrics without modification, creation, or deletion of data.
Attacks that exploit this kind of access
Get lactate threshold data. Critical for Norwegian double threshold. It is categorised as a Read tool in the Garmin Connect MCP MCP Server, which means it retrieves data without modifying state.
Register the Garmin Connect MCP server in PolicyLayer and add a rule for get_lactate_threshold: 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 MCP. Nothing to install.
get_lactate_threshold 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_lactate_threshold 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_lactate_threshold. 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_lactate_threshold is provided by the Garmin Connect MCP server (leewnsdud/garmin-connect-mcp). 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 →