list_dev_keys

List the API keys owned by your OpenGolf ID (prefixes only — never the secret). Requires an OpenGolf ID access_token from complete_sign_in.

Server OpenGolfAPI MCP Server opengolfapi/mcp-server
Category Read
Risk class Low
Parameters 00 required

What list_dev_keys does on OpenGolfAPI MCP Server

AI agents call list_dev_keys to retrieve information from OpenGolfAPI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_dev_keys needs a policy

This tool performs a read-only query operation that returns metadata about existing API keys associated with a user account. Although API key management could be sensitive in some contexts, the restriction to prefixes only (not secrets) and the read-only nature significantly limits the risk. An agent listing keys cannot abuse credentials directly, though it could inform subsequent malicious actions.

From the tool's definition The tool description states it 'List[s] the API keys' and explicitly notes 'prefixes only — never the secret', indicating it retrieves and displays existing data without modification or deletion.

Questions about list_dev_keys

What does the list_dev_keys tool do? +

List the API keys owned by your OpenGolf ID (prefixes only — never the secret). Requires an OpenGolf ID access_token from complete_sign_in. It is categorised as a Read tool in the OpenGolfAPI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_dev_keys? +

Register the OpenGolfAPI MCP Server MCP server in PolicyLayer and add a rule for list_dev_keys: 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 list_dev_keys? +

list_dev_keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_dev_keys? +

Yes. Add a rate_limit block to the list_dev_keys 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 list_dev_keys completely? +

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.