get_gear
AI agents call get_gear to retrieve information from Garmin MCP Server for Poke without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and context strongly suggest this retrieves gear information from Garmin Connect without modifying, deleting, or executing actions. No side effects are implied. Despite the empty description, the semantic consistency with other Read-category tools on the server and the standard 'get_' prefix pattern supports classification as Read with low severity.
From the tool's definition Tool name 'get_gear' indicates a retrieval operation. Sibling tools on the same server include 'get_activities' and 'count_activities', which are clearly Read operations. The naming convention is consistent with query/fetch semantics.
Attacks that exploit this kind of access
get_gear. It is categorised as a Read tool in the Garmin MCP Server for Poke MCP Server, which means it retrieves data without modifying state.
Register the Garmin MCP Server for Poke MCP server in PolicyLayer and add a rule for get_gear: 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.
get_gear 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_gear 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_gear. 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_gear 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 →