Register an https URL to receive OpenGolf domain events (e.g. session_settlement, event_settlement) the instant they happen — no polling. Requires OPENGOLFAPI_KEY. Each delivery is HMAC-signed (X-OG-Signature); verify the record content_hash where present. Owner-scoped: you only receive your own ...
AI agents use register_webhook to create or update resources in OpenGolfAPI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenGolfAPI MCP Server environment.
This tool creates a new webhook registration, which is a reversible Write action—the webhook can be deregistered. However, the severity is high because: (1) it establishes an ongoing channel for receiving sensitive domain events (session_settlement, event_settlement); (2) misuse could route tournament, competition, or financial settlement notifications to an attacker-controlled endpoint; (3) while owner-scoped, a…
From the tool's definition Tool registers (creates) a webhook endpoint configuration that will persistently receive events. Description states 'Register an https URL' and indicates it modifies server-side event delivery state, making it a Write operation that creates a new webhook…
Attacks that exploit this kind of access
Register an https URL to receive OpenGolf domain events (e.g. session_settlement, event_settlement) the instant they happen — no polling. Requires OPENGOLFAPI_KEY. Each delivery is HMAC-signed (X-OG-Signature); verify the record content_hash where present. Owner-scoped: you only receive your own events. It is categorised as a Write tool in the OpenGolfAPI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenGolfAPI MCP Server MCP server in PolicyLayer and add a rule for register_webhook: 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 OpenGolfAPI MCP Server. Nothing to install.
register_webhook 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 register_webhook 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 register_webhook. 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.
register_webhook is provided by the OpenGolfAPI MCP Server MCP server (opengolfapi/mcp-server). 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 →