find_orphan_cis
AI agents call find_orphan_cis to retrieve information from ServiceNow CMDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to search/query the CMDB for orphaned CIs (configuration items without proper relationships/dependencies). This is a read-only operation retrieving data with no modification or deletion capability. Severity is medium because identifying orphaned CIs could expose infrastructure details or reveal security gaps, but the read-only nature and lack of side effects places it below high.
From the tool's definition Tool name 'find_orphan_cis' indicates querying for orphaned configuration items in CMDB. No description provided, but context from server description shows this is part of 'querying' and 'dependency analysis' capabilities.
Attacks that exploit this kind of access
find_orphan_cis. It is categorised as a Read tool in the ServiceNow CMDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow CMDB MCP Server MCP server in PolicyLayer and add a rule for find_orphan_cis: 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.
find_orphan_cis 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 find_orphan_cis 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 find_orphan_cis. 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.
find_orphan_cis 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 →