datastore_runAggregationQuery · MCP Datastore Server MCP

WHAT IT DOES

What datastore_runAggregationQuery does on MCP Datastore Server

AI agents invoke datastore_runAggregationQuery to trigger actions in MCP Datastore 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 datastore_runAggregationQuery needs a policy

Aggregation queries execute database operations with computational side effects (aggregation logic, indexing traversal). Although not destructive or modifying, the tool's capability to run arbitrary aggregation logic makes it Execute rather than simple Read.

From the tool's definition Tool executes aggregation queries (count, sum, avg) on Datastore entities. The description explicitly uses 'run' and 'query', indicating dynamic execution of database operations whose results depend on query parameters.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

datastore_runAggregationQuery Rate-limited

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

FAQ

Questions about datastore_runAggregationQuery

What does the datastore_runAggregationQuery tool do? +

Run an aggregation query (count, sum, avg) on Datastore entities. It is categorised as a Execute tool in the MCP Datastore 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 datastore_runAggregationQuery? +

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

What risk level is datastore_runAggregationQuery? +

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

Can I rate-limit datastore_runAggregationQuery? +

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

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

datastore_runAggregationQuery is provided by the MCP Datastore Server MCP server (petekmet/mcp-gcp-datastore). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.