run_graphql_query · Advanced Hasura GraphQL MCP Server MCP

WHAT IT DOES

What run_graphql_query does on Advanced Hasura GraphQL MCP Server

AI agents invoke run_graphql_query 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_query needs a policy

Although labeled 'read-only', this tool executes arbitrary GraphQL queries determined by user input. GraphQL queries can perform complex operations including multiple nested resolvers, field authorization bypass scenarios, and resource-intensive aggregations that could overwhelm the endpoint.

From the tool's definition Executes a read-only GraphQL query against the Hasura endpoint

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_graphql_query Rate-limited

run_graphql_query 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_query": {
      "limits": [
        {
          "counter": "run_graphql_query_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_query

What does the run_graphql_query tool do? +

Executes a read-only GraphQL query against the Hasura endpoint. 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_query? +

Register the Advanced Hasura GraphQL MCP Server MCP server in PolicyLayer and add a rule for run_graphql_query: 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_query? +

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

Can I rate-limit run_graphql_query? +

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

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

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