Get hill score data between dates
AI agents call get_hill_score 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 retrieves fitness metrics (hill score data) within a specified date range. It performs a query operation that does not modify, delete, or execute any actions. The blast radius of misuse is minimal—an attacker could only access the user's historical hill score data, which is informational only. No data is created, modified, or destroyed, and no external operations are triggered.
From the tool's definition Tool name 'get_hill_score' and description 'Get hill score data between dates' indicate a retrieval operation with no side effects. The verb 'Get' and the data retrieval nature (querying historical hill score metrics) confirm this is a read-only action.
Attacks that exploit this kind of access
Get hill score data between dates. 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_hill_score: 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_hill_score 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_hill_score 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_hill_score. 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_hill_score is provided by the Garmin MCP Server MCP server (shubhaankar-sharma/garmin-mcp-railway). 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 →