Get user's preferred unit system from profile
AI agents call get_unit_system 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 only queries and retrieves the user's unit system preference from their Garmin profile. It does not create, modify, delete, or execute any operations. It has minimal blast radius if misused by an AI agent, as it only exposes a non-sensitive preference setting (metric vs. imperial units). This is a straightforward Read category tool.
From the tool's definition Tool name is "get_unit_system" and description states "Get user's preferred unit system from profile" - this retrieves a read-only preference setting with no modification or side effects.
Attacks that exploit this kind of access
Get user's preferred unit system from profile. 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_unit_system: 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_unit_system 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_unit_system 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_unit_system. 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_unit_system 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 →