Get alarms from all Garmin devices Returns all configured alarms with their schedules, sounds, and enabled status.
AI agents call get_device_alarms 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 alarm information from Garmin devices. It performs a read-only operation that returns alarm schedules, sounds, and enabled status without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an unauthorized actor could view alarm settings but cannot change device behavior or cause harm. This is a straightforward Read category tool.
From the tool's definition Tool name 'get_device_alarms' and description 'Get alarms from all Garmin devices' and 'Returns all configured alarms' — retrieves alarm configuration data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_device_alarms 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_alarms:
{
"version": "1",
"default": "deny",
"tools": {
"get_device_alarms": {}
}
}get_device_alarms 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 alarms from all Garmin devices Returns all configured alarms with their schedules, sounds, and enabled status. 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_alarms: 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_alarms 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_alarms 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_alarms. 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_alarms 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.