create_dev_key · OpenGolfAPI MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_dev_key does on OpenGolfAPI MCP Server

AI agents use create_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.

WHY IT NEEDS A POLICY

Why create_dev_key needs a policy

This tool creates a new API key credential, which is a reversible write operation (keys can be revoked or rotated). While it establishes access permissions, it does not execute code, delete data, or move financial resources.

From the tool's definition Tool description states it will 'mint an API key' and 'Returns the key ONCE', indicating creation of a new credential/resource. The scopes granted include 'read + contribute + keyless gross scoring', which establishes permissions for future operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_dev_key Rate-limited

create_dev_key stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_dev_key": {
      "limits": [
        {
          "counter": "create_dev_key_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches OpenGolfAPI MCP Server, so you can run agents against it safely.

FAQ

Questions about create_dev_key

What does the create_dev_key tool do? +

Sign up to build: mint an API key bound to your OpenGolf ID. Requires an OpenGolf ID access_token (from complete_sign_in) + the SAME email you signed in with. No OpenGolf ID, no key. Returns the key ONCE. Scope = read + contribute + keyless gross scoring. 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.

How do I enforce a policy on create_dev_key? +

Register the OpenGolfAPI MCP Server MCP server in PolicyLayer and add a rule for create_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.

What risk level is create_dev_key? +

create_dev_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_dev_key? +

Yes. Add a rate_limit block to the create_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.

How do I block create_dev_key completely? +

Set action: deny in the PolicyLayer policy for create_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.

What MCP server provides create_dev_key? +

create_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.