Get golf performance data and scorecards
AI agents call get_golf_data 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 golf performance metrics and scorecard data from the Garmin Connect service. It has no side effects—it queries and returns existing user data without creating, modifying, or deleting anything. The blast radius of misuse is minimal, as an AI agent could only access or exfiltrate the user's own golf activity history, not modify fitness records or trigger external actions.
From the tool's definition Tool name 'get_golf_data' and description 'Get golf performance data and scorecards' indicate data retrieval with no modification or deletion capability.
Attacks that exploit this kind of access
Get golf performance data and scorecards. 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_golf_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. Nothing to install.
get_golf_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_golf_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_golf_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_golf_data is provided by the Garmin MCP Server MCP server (j4sun/garmin-mcp). 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 →