run_graphql_mutation | PolicyLayer

WHAT IT DOES

What run_graphql_mutation does on Advanced Hasura GraphQL MCP Server

AI agents invoke run_graphql_mutation to trigger actions in Advanced Hasura GraphQL 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 run_graphql_mutation needs a policy

This tool runs arbitrary GraphQL mutations which can insert, update, or delete data. Since it spans Write, Destructive, and Execute categories, and the most severe applicable is Destructive (due to delete capability), but since the tool also executes arbitrary operations whose effects depend on arguments (mutations can be anything), Execute/Destructive both apply.

From the tool's definition Executes a GraphQL mutation to insert, update, or delete data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_graphql_mutation Rate-limited

run_graphql_mutation 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": {
    "run_graphql_mutation": {
      "limits": [
        {
          "counter": "run_graphql_mutation_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 Advanced Hasura GraphQL MCP Server, so you can run agents against it safely.

FAQ

Questions about run_graphql_mutation

What does the run_graphql_mutation tool do? +

Executes a GraphQL mutation to insert, update, or delete data. It is categorised as a Execute tool in the Advanced Hasura GraphQL 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 run_graphql_mutation? +

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

What risk level is run_graphql_mutation? +

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

Can I rate-limit run_graphql_mutation? +

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

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

run_graphql_mutation is provided by the Advanced Hasura GraphQL MCP Server MCP server (vikasversetest-debug/hasura_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.