compare_instances
Compare two configured ServiceNow instances: record counts for a table (with optional query) and/or a specific system property value. Useful for dev→prod drift detection and governance.
This record as markdown: /tools/nowaikit-servicenow-ai-toolkit/compare-instances.md
What compare_instances does on NowAIKit — ServiceNow AI Toolkit
AI agents call compare_instances 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_instances is rated Low
This tool retrieves and compares metadata about ServiceNow instances (record counts, system properties) to detect configuration drift. It performs only read operations with no side effects. The worst-case misuse would be information disclosure about system configuration, which is low severity compared to data modification or destructive actions.
From the tool's definition The tool description states it 'Compare[s] two configured ServiceNow instances: record counts for a table (with optional query) and/or a specific system property value.' The verbs are 'compare' and 'record counts' and 'check property values' — all data…
Attacks that exploit this kind of access
The rule that runs compare_instances 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_instances, this is the rule to start with:
compare_instances 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_instances call is checked against it from then on.
Questions about compare_instances
Compare two configured ServiceNow instances: record counts for a table (with optional query) and/or a specific system property value. Useful for dev→prod drift detection and governance. 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_instances: 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_instances 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_instances 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_instances. 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_instances 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