// SCAN REPORT

GolfBox MCP

10 tools. 2 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 2 Jul 2026

2 can modify or destroy data

8 read-only

10 tools total

Community server · catalogue entry verified 02/07/2026

How to control GolfBox MCP ↓

TOOL MAP

What GolfBox MCP exposes to your agents

Read (8) Write / Execute (1) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous GolfBox MCP tools

Destructive · High golfbox_cancel_booking Canceling a booking destroys or voids a confirmed reservation that cannot be automatically restored without manual intervention. Write · Medium golfbox_create_booking 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.

2 of GolfBox MCP's 10 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control GolfBox MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and GolfBox MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "golfbox_cancel_booking": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "golfbox_create_booking": {
    "limits": [
      {
        "counter": "golfbox_create_booking_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "golfbox_authenticate": {
    "limits": [
      {
        "counter": "golfbox_authenticate_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register GolfBox MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GOLFBOX →

Instant setup, no code required.

FULL CATALOGUE

All 10 GolfBox MCP tools

DESTRUCTIVE 1 tools

Destructive golfbox_cancel_booking Cancel a booking. Disabled unless write tools are explicitly enabled.

WRITE 1 tools

Write golfbox_create_booking Create a tee-time booking. Disabled unless write tools are explicitly enabled.

READ 8 tools

Read golfbox_authenticate Authenticate with the configured GolfBox adapter and validate the token where supported. Read golfbox_list_bookings List tee-time bookings for the authenticated GolfBox user. Read golfbox_list_clubs List clubs known by the configured GolfBox adapter. Read golfbox_list_tournaments List tournaments the authenticated GolfBox user is registered for or has participated in. Read golfbox_list_upcoming_tee_times List upcoming private tee times for the authenticated GolfBox user. Read golfbox_prepare_booking Validate and summarize a booking without creating it. Read golfbox_search_tee_time_players Search a club tee sheet for player names or booking text on a specific date. Read golfbox_search_tee_times Search available tee times for a club and date.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about GolfBox MCP

Can an AI agent delete data through the GolfBox MCP server? +

Yes. The GolfBox MCP server exposes 1 destructive tools including golfbox_cancel_booking. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through GolfBox MCP? +

The GolfBox MCP server has 1 write tools including golfbox_create_booking. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach GolfBox MCP.

How many tools does the GolfBox MCP server expose? +

10 tools across 3 categories: Destructive, Read, Write. 8 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on GolfBox MCP? +

Register the GolfBox MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every GolfBox MCP tool call.

Deterministic rules across all 10 GolfBox MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GOLFBOX →

Instant setup, no code required.

10 GolfBox MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.