Create a relationship between two CIs
AI agents use cmdb_relationship_create to create or update resources in ServiceNow MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow MCP Server environment.
Creating a relationship between Configuration Items is a write operation that modifies the CMDB state. It is reversible (the relationship can be deleted), so it is classified as Write rather than Destructive.
From the tool's definition Tool name contains 'create' and description states 'Create a relationship between two CIs' — this is a reversible modification operation that establishes a new association in the CMDB (Configuration Management Database).
Attacks that exploit this kind of access
Create a relationship between two CIs. It is categorised as a Write tool in the ServiceNow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for cmdb_relationship_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 MCP Server. Nothing to install.
cmdb_relationship_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 cmdb_relationship_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 cmdb_relationship_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.
cmdb_relationship_create is provided by the ServiceNow MCP Server MCP server (schwarztim/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 →