cmdb_reconcile
Act on duplicate, stale, or orphan CIs — merge, retire, or remove (requires CMDB_WRITE_ENABLED). Supports dry_run mode.
This record as markdown: /tools/servicenow-mcp-server/cmdb-reconcile.md
What cmdb_reconcile does on ServiceNow MCP Server
AI agents call cmdb_reconcile to permanently remove resources in ServiceNow MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cmdb_reconcile is rated Critical
While the tool offers a dry_run mode for safety, the primary action set includes irreversible deletion and retirement of configuration records. Misuse could orphan infrastructure tracking, break dependency chains, and cause cascading system failures. This is more severe than Execute because the effects are permanent data destruction in a critical system database, not just code execution with reversible outcomes.
From the tool's definition Tool description states it can 'merge, retire, or remove' CIs (Configuration Items). 'Remove' and 'retire' are irreversible operations on critical infrastructure data.
Attacks that exploit this kind of access
The rule that runs cmdb_reconcile 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 cmdb_reconcile, this is the rule to start with:
cmdb_reconcile is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every cmdb_reconcile call is checked against it from then on.
Questions about cmdb_reconcile
Act on duplicate, stale, or orphan CIs — merge, retire, or remove (requires CMDB_WRITE_ENABLED). Supports dry_run mode. It is categorised as a Destructive tool in the ServiceNow MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for cmdb_reconcile: 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.
cmdb_reconcile is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cmdb_reconcile 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 cmdb_reconcile. 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.
cmdb_reconcile 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.
More on ServiceNow MCP Server, and thousands of servers like it.
Across the catalogue