oc_execute_graphql · OpenCollective MCP Server MCP

WHAT IT DOES

What oc_execute_graphql does on OpenCollective MCP Server

AI agents invoke oc_execute_graphql to trigger actions in OpenCollective 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 oc_execute_graphql needs a policy

While the tool itself does not directly move money, it executes arbitrary GraphQL mutations against a financial API. Combined with the server's role in managing expenses and financial records, an AI agent could use raw mutations to modify expense data, alter transaction records, or trigger unintended financial operations.

From the tool's definition Tool name includes 'execute' and description explicitly states 'Execute a raw GraphQL query or mutation against the OpenCollective API v2.' The ability to run arbitrary mutations against a financial platform (OpenCollective manages collective funds, expenses,…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

oc_execute_graphql Rate-limited

oc_execute_graphql 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": {
    "oc_execute_graphql": {
      "limits": [
        {
          "counter": "oc_execute_graphql_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 OpenCollective MCP Server, so you can run agents against it safely.

FAQ

Questions about oc_execute_graphql

What does the oc_execute_graphql tool do? +

Execute a raw GraphQL query or mutation against the OpenCollective API v2. It is categorised as a Execute tool in the OpenCollective 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 oc_execute_graphql? +

Register the OpenCollective MCP Server MCP server in PolicyLayer and add a rule for oc_execute_graphql: 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 OpenCollective MCP Server. Nothing to install.

What risk level is oc_execute_graphql? +

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

Can I rate-limit oc_execute_graphql? +

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

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

oc_execute_graphql is provided by the OpenCollective MCP Server MCP server (theepicsaxguy/opencollective-hetzner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.