record_attempt · OpenGolfAPI MCP Server MCP: Risk & Policy

WHAT IT DOES

What record_attempt does on OpenGolfAPI MCP Server

AI agents use record_attempt 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 record_attempt needs a policy

This tool writes/creates a score or value record within a competition. It is described as idempotent, meaning repeated calls produce the same result without additional side effects, but it does modify competition data by recording an attempt. No irreversible deletion or financial transaction is involved, making Write the appropriate category. Misuse could corrupt competition scores, warranting medium severity.

From the tool's definition 'Record an Attempt in a Competition (a score for stroke formats, a side-game value for shot formats). Idempotent.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_attempt Rate-limited

record_attempt 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": {
    "record_attempt": {
      "limits": [
        {
          "counter": "record_attempt_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 record_attempt

What does the record_attempt tool do? +

Record an Attempt in a Competition (a score for stroke formats, a side-game value for shot formats). Idempotent. Requires OPENGOLFAPI_KEY. 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 record_attempt? +

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

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

Can I rate-limit record_attempt? +

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

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

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