Low Risk

get_earned_badges

Get all earned badges and achievements

How to control get_earned_badges ↓

AI agents call get_earned_badges to retrieve information from Garmin Connect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and returns badge/achievement data from Garmin Connect. It performs a read-only operation with no side effects—it neither modifies, deletes, nor executes operations. The data retrieved is non-sensitive achievement metadata, presenting minimal risk if misused by an AI agent.

From the tool's definition Tool name 'get_earned_badges' and description 'Get all earned badges and achievements' indicate a retrieval operation with no modification of data.

Documented attack patterns abuse exactly the kind of access get_earned_badges gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Garmin Connect, and nothing reaches the server without passing your rules. This is the rule we recommend for get_earned_badges:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_earned_badges": {}
  }
}

get_earned_badges is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Garmin Connect — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_earned_badges tool do? +

Get all earned badges and achievements. It is categorised as a Read tool in the Garmin Connect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_earned_badges? +

Register the Garmin Connect 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 Connect. Nothing to install.

What risk level is get_earned_badges? +

get_earned_badges is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_earned_badges? +

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.

How do I block get_earned_badges completely? +

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.

What MCP server provides get_earned_badges? +

get_earned_badges is provided by the Garmin Connect MCP server (nicolasvegam/garmin-connect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Garmin Connect tool call.

Deterministic rules across all 97 Garmin Connect tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

97 Garmin Connect tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.