record_consent · OpenGolfAPI MCP Server MCP: Risk & Policy

WHAT IT DOES

What record_consent does on OpenGolfAPI MCP Server

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

Recording consent is a Write operation as it creates or modifies a data record (the player's consent status). The description is truncated/uninformative beyond the tool name, which slightly lowers confidence. Misuse could result in falsely recording or altering a player's consent, which has privacy and legal implications, warranting medium severity.

From the tool's definition 'record_consent' — records a player's consent, implying creating or storing a consent record

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_consent Rate-limited

record_consent 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_consent": {
      "limits": [
        {
          "counter": "record_consent_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_consent

What does the record_consent tool do? +

Record a player\. 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_consent? +

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

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

Can I rate-limit record_consent? +

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

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

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