The safe playbook for building on OpenGolfAPI and contributing data the right way. Call once before contributing.
AI agents call how_to_build 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 retrieves instructional/documentation content (a 'playbook') intended to guide developers. It has no write, execute, destructive, or financial actions. The description suggests it returns static guidance text. Severity is low as misuse would only result in reading documentation.
From the tool's definition 'safe playbook for building on OpenGolfAPI' and 'Call once before contributing' — implies retrieval of documentation/instructions with no side effects
Attacks that exploit this kind of access
The safe playbook for building on OpenGolfAPI and contributing data the right way. Call once before contributing. 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 how_to_build: 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.
how_to_build 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 how_to_build 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 how_to_build. 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.
how_to_build 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 →