Low Risk

aggregate_query

Run aggregate functions (COUNT, AVG, MIN, MAX, SUM) on any ServiceNow table

How to control aggregate_query ↓

What aggregate_query does on Now Sdk Ext

AI agents call aggregate_query to retrieve information from Now Sdk Ext without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why aggregate_query needs a policy

Aggregate functions (COUNT, AVG, MIN, MAX, SUM) are inherently read-only operations that compute statistics over existing data. They do not create, modify, delete, or execute code. While they can query 'any ServiceNow table' (broad scope), the operation itself has no side effects and only returns computed values. Low severity because the blast radius of misuse is limited to information disclosure.

From the tool's definition Tool description: 'Run aggregate functions (COUNT, AVG, MIN, MAX, SUM) on any ServiceNow table' - these are read-only aggregate operations that retrieve computed statistics without modifying data.

Documented attack patterns abuse exactly the kind of access aggregate_query gives an agent:

How to control aggregate_query

PolicyLayer is an MCP gateway — it sits between your AI agents and Now Sdk Ext, and nothing reaches the server without passing your rules. This is the rule we recommend for aggregate_query:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "aggregate_query": {}
  }
}

aggregate_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Now Sdk Ext — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about aggregate_query

What does the aggregate_query tool do? +

Run aggregate functions (COUNT, AVG, MIN, MAX, SUM) on any ServiceNow table. It is categorised as a Read tool in the Now Sdk Ext MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on aggregate_query? +

Register the Now Sdk Ext MCP server in PolicyLayer and add a rule for aggregate_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 Now Sdk Ext. Nothing to install.

What risk level is aggregate_query? +

aggregate_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit aggregate_query? +

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

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

aggregate_query is provided by the Now Sdk Ext MCP server (sonisoft-cnanda/now-sdk-ext-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Now Sdk Ext tool call.

Start from Now Sdk Ext, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

86 Now Sdk Ext tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.