Request reload of epoch data
AI agents invoke request_reload to trigger actions in Garmin MCP Server for Poke. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool requests a reload operation, which triggers an external action on the Garmin Connect service rather than simply reading or writing data. It likely causes the system to re-fetch or reprocess epoch (time-period) data. The description is minimal, lowering confidence. Severity is medium as misuse could cause repeated/unintended reload operations affecting data processing pipelines.
From the tool's definition 'Request reload of epoch data' — triggers an external operation (reload/refresh) on Garmin Connect epoch data
Attacks that exploit this kind of access
Request reload of epoch data. It is categorised as a Execute tool in the Garmin MCP Server for Poke MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Garmin MCP Server for Poke MCP server in PolicyLayer and add a rule for request_reload: 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 for Poke. Nothing to install.
request_reload is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the request_reload 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 request_reload. 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.
request_reload is provided by the Garmin MCP Server for Poke MCP server (theol0403/garmin-mcp-poke). 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 →