file_claim · OpenGolfAPI MCP Server MCP: Risk & Policy

WHAT IT DOES

What file_claim does on OpenGolfAPI MCP Server

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

Filing a claim creates a new entry in a trust ledger with lifecycle states, which is a persistent write operation. Claims relate to ownership, attestation, and identity — misuse could fraudulently assert ownership or identity over golf course records. While not directly financial or irreversibly destructive, the trust/identity implications give it high severity.

From the tool's definition File a Claim in the trust ledger (ownership, attestation, identity, record, correction). Lifecycle open→accepted→disputed→verified. Requires OPENGOLFAPI_KEY to file.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

file_claim Rate-limited

file_claim 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": {
    "file_claim": {
      "limits": [
        {
          "counter": "file_claim_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 file_claim

What does the file_claim tool do? +

File a Claim in the trust ledger (ownership, attestation, identity, record, correction). Lifecycle open→accepted→disputed→verified. Reads are free. Requires OPENGOLFAPI_KEY to file. 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 file_claim? +

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

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

Can I rate-limit file_claim? +

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

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

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