Broadcast a player\
AI agents use set_beacon 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.
The tool appears to write/create beacon data linked to a player profile. While the description is incomplete ('Broadcast a player\' appears truncated), the name 'set_beacon' combined with the context of other tools like 'find_beacons' indicates this creates or modifies beacon state. This is reversible (unlike Destructive), doesn't execute arbitrary code (unlike Execute), and has no financial impact.
From the tool's definition Tool name 'set_beacon' with description 'Broadcast a player' suggests creating or modifying a beacon record associated with a player, which is a reversible write operation.
Attacks that exploit this kind of access
Broadcast a player\. 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 set_beacon: 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.
set_beacon 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 set_beacon 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 set_beacon. 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.
set_beacon 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 →