Get settings for a specific Garmin device Returns device configuration including time/date format, units, activity tracking settings, and alarm information. Args: device_id: Device ID (optional; defaults to the most recently used device when omitted; can be obtained from get_devices or get_device...
AI agents call get_device_settings 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 device configuration data without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that poses minimal risk as device settings are non-sensitive metadata (time format, units, activity tracking preferences). The narrow scope and read-only nature warrant a 'low' severity classification.
From the tool's definition Tool description states it 'Get settings for a specific Garmin device' and 'Returns device configuration including time/date format, units, activity tracking settings, and alarm information.' The verb 'Get' and 'Returns' indicate data retrieval with no…
Documented attack patterns abuse exactly the kind of access get_device_settings gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Garmin MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_device_settings:
{
"version": "1",
"default": "deny",
"tools": {
"get_device_settings": {}
}
}get_device_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 settings for a specific Garmin device Returns device configuration including time/date format, units, activity tracking settings, and alarm information. Args: device_id: Device ID (optional; defaults to the most recently used device when omitted; can be obtained from get_devices or get_device_last_used). 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_device_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 MCP Server. Nothing to install.
get_device_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_device_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_device_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_device_settings is provided by the Garmin MCP Server MCP server (taxuspt/garmin_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 126 Garmin MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
126 Garmin MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.