Get Garmin Connect goals (active, future, or past)
AI agents call get_goals 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 user fitness/health goals data from Garmin Connect without modifying, deleting, or executing external operations. It is purely informational with read-only semantics. The blast radius of misuse is minimal — an AI agent could only view the user's goal information, which does not expose sensitive financial data, enable code execution, or permit destructive actions.
From the tool's definition Tool name is 'get_goals' and description states 'Get Garmin Connect goals' — uses retrieval verb 'Get' with no indication of modification, deletion, or execution of arbitrary operations.
Attacks that exploit this kind of access
Get Garmin Connect goals (active, future, or past). 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_goals: 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_goals 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_goals 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_goals. 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_goals is provided by the Garmin MCP Server MCP server (jbaker48/garmin-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 →