Read back your own contributed shots (by player or session). Requires OPENGOLFAPI_KEY.
AI agents call get_my_shots to retrieve information from OpenGolfAPI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves historical shot data that the authenticated user has previously contributed. It performs no creation, modification, deletion, or execution of commands. The scope is limited to the user's own records, minimizing blast radius. Authentication requirement further reduces risk.
From the tool's definition Tool description explicitly states 'Read back your own contributed shots' — retrieves data with no modification or side effects. Requires authentication (OPENGOLFAPI_KEY) which limits access to user's own data.
Attacks that exploit this kind of access
Read back your own contributed shots (by player or session). Requires OPENGOLFAPI_KEY. It is categorised as a Read tool in the OpenGolfAPI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenGolfAPI MCP Server MCP server in PolicyLayer and add a rule for get_my_shots: 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 OpenGolfAPI MCP Server. Nothing to install.
get_my_shots 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_my_shots 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_my_shots. 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_my_shots is provided by the OpenGolfAPI MCP Server MCP server (opengolfapi/mcp-server). 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 →