Get earned badges for user
AI agents call get_earned_badges 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 queries and retrieves existing fitness achievement data (badges) from the user's Garmin Connect account. It performs no write, execution, destructive, or financial operations. The verb 'get' combined with the retrieval-only nature of badge data clearly indicates a Read category classification. The blast radius of misuse is minimal—unauthorized disclosure of personal achievement badges.
From the tool's definition Tool is named 'get_earned_badges' with description 'Get earned badges for user' — a retrieval operation with 'get' as the primary verb, retrieving badge achievement data with no modification or side effects.
Attacks that exploit this kind of access
Get earned badges for user. 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_earned_badges: 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_earned_badges 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_earned_badges 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_earned_badges. 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_earned_badges is provided by the Garmin MCP Server MCP server (shubhaankar-sharma/garmin-mcp-railway). 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 →