aggregate_data · Advanced Hasura GraphQL MCP Server MCP

WHAT IT DOES

What aggregate_data does on Advanced Hasura GraphQL MCP Server

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

This tool executes aggregation queries against a GraphQL/database endpoint. While it is primarily a read-oriented operation (retrieving computed statistics), it executes operations against an external system with results that depend on the arguments provided. It does not modify data, but 'Execute' is the appropriate category as it runs queries against an external service.

From the tool's definition Performs a simple aggregation (count, sum, avg, min, max)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

aggregate_data Rate-limited

aggregate_data 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": {
    "aggregate_data": {
      "limits": [
        {
          "counter": "aggregate_data_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 aggregate_data

What does the aggregate_data tool do? +

Performs a simple aggregation (count, sum, avg, min, max). 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 aggregate_data? +

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

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

Can I rate-limit aggregate_data? +

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

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

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