confirm_ci_create
AI agents use confirm_ci_create to create or update resources in ServiceNow CMDB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow CMDB MCP Server environment.
The 'confirm_ci_create' function creates new CIs in the CMDB, which modifies the database state reversibly. This is a Write operation—data is added but could theoretically be removed. Severity is medium because improper CI creation could pollute the CMDB with incorrect entries, affecting downstream dependency analysis and health auditing, but the impact is localized to CMDB records and reversible.
From the tool's definition Tool name 'confirm_ci_create' indicates creation of a Configuration Item (CI) in ServiceNow CMDB. Tool description is empty, limiting direct evidence.
Attacks that exploit this kind of access
confirm_ci_create. It is categorised as a Write tool in the ServiceNow CMDB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow CMDB MCP Server MCP server in PolicyLayer and add a rule for confirm_ci_create: 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 CMDB MCP Server. Nothing to install.
confirm_ci_create 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 confirm_ci_create 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 confirm_ci_create. 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.
confirm_ci_create is provided by the ServiceNow CMDB MCP Server MCP server (ketiil/mcp-cmdb). 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 →