Get adhoc challenges data
AI agents call get_adhoc_challenges 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 challenge data from Garmin Connect without any side effects. It matches the 'Read' category: retrieves or queries data with no side effects. Severity is low because fitness challenge metadata poses minimal risk if accessed by an AI agent—no financial impact, no destructive capability, and minimal privacy sensitivity compared to sensitive health records.
From the tool's definition Tool name 'get_adhoc_challenges' with description 'Get adhoc challenges data' indicates a retrieval operation with no modification of data. The verb 'Get' and context of the Garmin server (which exposes fitness/health data) confirm this is a query operation.
Attacks that exploit this kind of access
Get adhoc challenges data. 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_adhoc_challenges: 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_adhoc_challenges 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_adhoc_challenges 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_adhoc_challenges. 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_adhoc_challenges 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 →