List upcoming private tee times for the authenticated GolfBox user.
AI agents call golfbox_list_upcoming_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 queries and returns existing tee time data for the authenticated user. It performs data retrieval only, matching the Read category definition (search, list, get, fetch). The blast radius is minimal — an agent can view tee time information but cannot create, modify, delete, or execute operations. Severity is low due to the read-only nature and limited scope to the authenticated user's own data.
From the tool's definition Tool name contains 'list' and description states 'List upcoming private tee times' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List upcoming private tee times for the authenticated GolfBox user. 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_list_upcoming_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_list_upcoming_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_list_upcoming_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_list_upcoming_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_list_upcoming_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 →