get_device_solar_data
AI agents call get_device_solar_data 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 retrieves solar data from a Garmin device—a query operation with no side effects. The 'get_' prefix strongly indicates a read operation. While the description is empty, the naming convention and sibling tools provide sufficient context to classify with high confidence as Read category. Read operations carry low severity since they only expose data without modifying or deleting it.
From the tool's definition Tool name 'get_device_solar_data' indicates data retrieval (get_ prefix). Sibling tools like 'get_activities' and 'count_activities' are clearly Read operations.
Attacks that exploit this kind of access
get_device_solar_data. 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_device_solar_data: 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_device_solar_data 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_solar_data 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_solar_data. 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_solar_data 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 →