compare_record_counts

Compare record counts across multiple ServiceNow tables or time periods — useful for capacity planning

SERVERServiceNow MCP Server SOURCE@aartiq/servicenow-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/servicenow-mcp-server/compare-record-counts.md

WHAT IT DOES

What compare_record_counts does on ServiceNow MCP Server

AI agents call compare_record_counts 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.

RISK

Why compare_record_counts is rated Low

This tool retrieves and analyzes data (record counts) without modifying, deleting, or executing operations on the underlying records. It is purely informational and supports reporting/analytics workflows. The most severe impact of misuse would be data exposure or reconnaissance, not modification or destruction.

From the tool's definition The tool 'compare_record_counts' performs a comparison operation across ServiceNow tables or time periods to retrieve and analyze record counts. The description explicitly states it is 'useful for capacity planning,' which is a read-only analytical use case.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs compare_record_counts 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 compare_record_counts, this is the rule to start with:

compare_record_counts Allowed

compare_record_counts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every compare_record_counts call is checked against it from then on.

FAQ

Questions about compare_record_counts

What does the compare_record_counts tool do? +

Compare record counts across multiple ServiceNow tables or time periods — useful for capacity planning. It is categorised as a Read tool in the ServiceNow MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on compare_record_counts? +

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

What risk level is compare_record_counts? +

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

Can I rate-limit compare_record_counts? +

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

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

compare_record_counts is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ServiceNow MCP Server, and thousands of servers like it.

This server

All 365 ServiceNow MCP Server tools →

Across the catalogue

compare_images on Percepta MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →