snow_reconcile_ci
[DEPRECATED - use snow_cmdb_identify_reconcile] Does not reconcile. PUTs the given fields onto base cmdb_ci for one sys_id and echoes reconciliation_rule back untouched — no identifier or reconciliation rule runs, no Source [sys_object_source] row is written, and class-specific fields are dropped...
This record as markdown: /tools/serac/snow-reconcile-ci.md
What snow_reconcile_ci does on Serac
AI agents use snow_reconcile_ci to create or update resources in Serac, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Serac environment.
Why snow_reconcile_ci is rated Medium
Modifies ServiceNow CMDB configuration items irreversibly without proper reconciliation validation.
From the tool's definition PUTs given fields onto base cmdb_ci for one sys_id
Attacks that exploit this kind of access
The rule that runs snow_reconcile_ci safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_reconcile_ci, this is the rule to start with:
snow_reconcile_ci stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Serac, apply this rule, and every snow_reconcile_ci call is checked against it from then on.
Questions about snow_reconcile_ci
[DEPRECATED - use snow_cmdb_identify_reconcile] Does not reconcile. PUTs the given fields onto base cmdb_ci for one sys_id and echoes reconciliation_rule back untouched — no identifier or reconciliation rule runs, no Source [sys_object_source] row is written, and class-specific fields are dropped. Use snow_cmdb_identify_reconcile instead, which posts the payload to the Identification and Reconciliation Engine. Kept only for callers that already depend on this plain cmdb_ci update. It is categorised as a Write tool in the Serac MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Serac MCP server in PolicyLayer and add a rule for snow_reconcile_ci: 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 Serac. Nothing to install.
snow_reconcile_ci is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the snow_reconcile_ci 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 snow_reconcile_ci. 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.
snow_reconcile_ci is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Serac, and thousands of servers like it.
This server
Across the catalogue