Create a tee-time booking. Disabled unless write tools are explicitly enabled.
AI agents use golfbox_create_booking to create or update resources in GolfBox MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GolfBox MCP environment.
Creating a booking is a reversible write operation that modifies the booking system state (new record inserted) but does not irreversibly delete data or commit financial transactions.
From the tool's definition Tool description explicitly states it will 'Create a tee-time booking', and notes it is 'Disabled unless write tools are explicitly enabled', confirming it modifies data by creating a new booking record.
Attacks that exploit this kind of access
Create a tee-time booking. Disabled unless write tools are explicitly enabled. It is categorised as a Write tool in the GolfBox MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GolfBox MCP server in PolicyLayer and add a rule for golfbox_create_booking: 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_create_booking is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the golfbox_create_booking 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_create_booking. 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_create_booking 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 →