Low Risk

get_device_last_used

Get the last used Garmin device info

How to control get_device_last_used ↓

AI agents call get_device_last_used 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 retrieves device metadata (which Garmin device was last used) from the user's Garmin Connect account. It is a read-only operation with no capability to modify, delete, execute code, or move money. The information returned is non-sensitive device usage metadata.

From the tool's definition Tool name 'get_device_last_used' and description 'Get the last used Garmin device info' indicate a query operation that retrieves information without modification or side effects.

Documented attack patterns abuse exactly the kind of access get_device_last_used 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_device_last_used:

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

get_device_last_used 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_device_last_used tool do? +

Get the last used Garmin device info. 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_device_last_used? +

Register the Garmin Connect MCP server in PolicyLayer and add a rule for get_device_last_used: 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_device_last_used? +

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

Can I rate-limit get_device_last_used? +

Yes. Add a rate_limit block to the get_device_last_used 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_device_last_used completely? +

Set action: deny in the PolicyLayer policy for get_device_last_used. 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_device_last_used? +

get_device_last_used 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.