aggregate_records

What aggregate_records does on ServiceNow MCP Server

AI agents call aggregate_records to retrieve information from ServiceNow MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why aggregate_records is rated Low

The tool name indicates aggregation functionality, which is a read operation that retrieves and summarizes data without side effects. The lack of description lowers confidence slightly, but ServiceNow aggregation functions are typically read-only query operations. Severity is low as aggregation operations on CMDB/table data have no destructive or systemic impact if misused.

From the tool's definition Tool name 'aggregate_records' suggests data aggregation/summarization operations. No description provided, but 'aggregate' typically implies querying and computing statistics on existing data without modification.

The rule that runs aggregate_records safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For aggregate_records, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "aggregate_records": {}
  }
}

Questions about aggregate_records