compare_record_counts
Compare record counts across multiple ServiceNow tables or time periods — useful for capacity planning
This record as markdown: /tools/nowaikit-servicenow-ai-toolkit/compare-record-counts.md
What compare_record_counts does on NowAIKit — ServiceNow AI Toolkit
AI agents call compare_record_counts to retrieve information from NowAIKit — ServiceNow AI Toolkit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why compare_record_counts is rated Low
This tool queries existing data to provide metrics for capacity planning purposes. It retrieves information without creating, modifying, deleting, or executing operations that would cause side effects. The blast radius of misuse is minimal — an agent could retrieve operational metrics but cannot corrupt, destroy, or compromise data integrity or create unauthorized changes.
From the tool's definition Tool performs comparison of record counts across ServiceNow tables or time periods — a query and analysis operation with no modification of data.
Attacks that exploit this kind of access
The rule that runs compare_record_counts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and NowAIKit — ServiceNow AI Toolkit, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect NowAIKit — ServiceNow AI Toolkit, apply this rule, and every compare_record_counts call is checked against it from then on.
Questions about compare_record_counts
Compare record counts across multiple ServiceNow tables or time periods — useful for capacity planning. It is categorised as a Read tool in the NowAIKit — ServiceNow AI Toolkit MCP Server, which means it retrieves data without modifying state.
Register the NowAIKit — ServiceNow AI Toolkit 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 NowAIKit — ServiceNow AI Toolkit. Nothing to install.
compare_record_counts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
compare_record_counts is provided by the NowAIKit — ServiceNow AI Toolkit MCP server (nowaikit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on NowAIKit — ServiceNow AI Toolkit, and thousands of servers like it.
This server
Across the catalogue