finalize_competition · OpenGolfAPI MCP Server MCP

WHAT IT DOES

What finalize_competition does on OpenGolfAPI MCP Server

AI agents invoke finalize_competition to trigger actions in OpenGolfAPI MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why finalize_competition needs a policy

This tool executes a computational kernel over competition data and stores the result, triggering an external operation with persistent side effects. Finalizing a competition is likely irreversible in practice (results are locked in), but the description focuses on running a process and storing output rather than deletion.

From the tool's definition 'Finalize a Competition — run the format kernel over its attempts and store the gross Result'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

finalize_competition Rate-limited

finalize_competition stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "finalize_competition": {
      "limits": [
        {
          "counter": "finalize_competition_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 finalize_competition

What does the finalize_competition tool do? +

Finalize a Competition — run the format kernel over its attempts and store the gross Result. Requires OPENGOLFAPI_KEY. It is categorised as a Execute tool in the OpenGolfAPI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on finalize_competition? +

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

finalize_competition is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit finalize_competition? +

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

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

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