Search available tee times for a club and date.
AI agents call golfbox_search_tee_times to retrieve information from GolfBox MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search/query operation to retrieve available tee times. It has no side effects—it does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal; an AI agent querying for tee times cannot cause harm beyond potentially accessing information it shouldn't see, which is a low-severity concern in a golf booking context.
From the tool's definition Tool name 'golfbox_search_tee_times' and description 'Search available tee times for a club and date' indicate a query operation that retrieves information without modifying any data.
Attacks that exploit this kind of access
Search available tee times for a club and date. It is categorised as a Read tool in the GolfBox MCP MCP Server, which means it retrieves data without modifying state.
Register the GolfBox MCP server in PolicyLayer and add a rule for golfbox_search_tee_times: 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 GolfBox MCP. Nothing to install.
golfbox_search_tee_times 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 golfbox_search_tee_times 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 golfbox_search_tee_times. 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.
golfbox_search_tee_times is provided by the GolfBox MCP server (j4hr3n/golfbox-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 →