List tournaments the authenticated GolfBox user is registered for or has participated in.
AI agents call golfbox_list_tournaments 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 retrieves and queries tournament registration/participation data for an authenticated user. It performs no state changes, has no irreversible effects, and carries minimal risk even if called inappropriately by an AI agent. Classification as Read with low severity is appropriate.
From the tool's definition Tool name 'list_tournaments' and description 'List tournaments the authenticated GolfBox user is registered for or has participated in' indicate a pure retrieval operation with no side effects.
Attacks that exploit this kind of access
List tournaments the authenticated GolfBox user is registered for or has participated in. 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_tournaments: 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_tournaments 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_tournaments 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_tournaments. 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_tournaments 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 →