Compare record counts across multiple ServiceNow tables or time periods — useful for capacity planning
AI agents call compare_record_counts to retrieve information from ServiceNow-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and compares aggregate data (record counts) from ServiceNow tables without creating, modifying, deleting, or executing operations. It is a straightforward read operation used for analysis and capacity planning. The blast radius is minimal—misuse would only expose count information already accessible to system users with appropriate permissions.
From the tool's definition Tool name 'compare_record_counts' and description 'Compare record counts across multiple ServiceNow tables or time periods' indicate a query/retrieval operation with no modification or deletion capability.
Attacks that exploit this kind of access
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 MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow- 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. 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 ServiceNow- MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →