Get nearby points of interest for a course (hotels, restaurants, airports) within ~20 miles. ODbL licensed.
AI agents call get_nearby 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 queries and retrieves location-based information about nearby amenities. It has no side effects, does not modify data, and presents minimal risk even if misused by an AI agent. The blast radius is limited to exposure of publicly available geographic and business location data.
From the tool's definition Tool retrieves 'nearby points of interest for a course (hotels, restaurants, airports)' with no modification or deletion of data. The geographic query is read-only with ODbL licensed data.
Attacks that exploit this kind of access
Get nearby points of interest for a course (hotels, restaurants, airports) within ~20 miles. ODbL licensed. 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_nearby: 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_nearby 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_nearby 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_nearby. 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_nearby 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 →