Confirm your OpenGolf ID on an EXISTING (legacy) key — the simple
AI agents use link_dev_key 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 modifies or updates an existing developer key by linking/confirming an OpenGolf ID to it. It's a reversible write operation (associating an identity with a key), not destructive. Severity is medium because misuse could associate a wrong identity with a developer key, potentially granting unauthorized access.
From the tool's definition Confirm your OpenGolf ID on an EXISTING (legacy) key
Attacks that exploit this kind of access
Confirm your OpenGolf ID on an EXISTING (legacy) key — the simple. 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 link_dev_key: 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.
link_dev_key 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 link_dev_key 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 link_dev_key. 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.
link_dev_key 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 →