Get user settings: measurement system, time/date format, sleep schedule, HR zones, hydration preferences
AI agents call get_user_settings 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.
This tool retrieves user preference and configuration data with no side effects. It performs a query operation that does not create, modify, delete, or execute anything. The blast radius of misuse is minimal—an AI agent could learn user preferences but cannot alter them or trigger external actions. Classification as Read is appropriate.
From the tool's definition Tool name 'get_user_settings' and description 'Get user settings' indicate retrieval only. No modification, deletion, or execution keywords present.
Documented attack patterns abuse exactly the kind of access get_user_settings 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_user_settings:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_settings": {}
}
}get_user_settings is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get user settings: measurement system, time/date format, sleep schedule, HR zones, hydration preferences. It is categorised as a Read tool in the Garmin Connect MCP Server, which means it retrieves data without modifying state.
Register the Garmin Connect MCP server in PolicyLayer and add a rule for get_user_settings: 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.
get_user_settings 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_user_settings 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_user_settings. 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_user_settings 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.
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.