Get user summary data (compatible with garminconnect-ha)
AI agents call get_user_summary to retrieve information from Garmin MCP Server for Poke 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 user summary data from Garmin Connect without creating, modifying, deleting, or executing operations. The data exposure risk is low because summary data typically contains aggregated, non-sensitive information. No side effects or irreversible actions are possible.
From the tool's definition 'Get user summary data' – retrieves summary information without modification. The verb 'get' and context of 'summary data' indicate a read-only query operation.
Attacks that exploit this kind of access
Get user summary data (compatible with garminconnect-ha). It is categorised as a Read tool in the Garmin MCP Server for Poke MCP Server, which means it retrieves data without modifying state.
Register the Garmin MCP Server for Poke MCP server in PolicyLayer and add a rule for get_user_summary: 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 for Poke. Nothing to install.
get_user_summary 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_summary 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_summary. 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_summary is provided by the Garmin MCP Server for Poke MCP server (theol0403/garmin-mcp-poke). 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 →