cmdb_find_stale

Find CIs not updated within a given number of days that are still operational

SERVERServiceNow MCP Server SOURCE@aartiq/servicenow-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/servicenow-mcp-server/cmdb-find-stale.md

WHAT IT DOES

What cmdb_find_stale does on ServiceNow MCP Server

AI agents call cmdb_find_stale to retrieve information from ServiceNow MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why cmdb_find_stale is rated Low

This tool retrieves and filters configuration management database records based on staleness criteria. It has no side effects—it does not modify, delete, execute code, or commit financial actions. The blast radius is minimal; misuse would only expose or report stale asset data, not alter infrastructure or trigger unintended operations.

From the tool's definition Tool performs a find/query operation to identify CIs (Configuration Items) not updated within a specified timeframe; 'Find' and 'CIs not updated' indicate data retrieval with no modification, deletion, or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cmdb_find_stale 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_find_stale, this is the rule to start with:

cmdb_find_stale Allowed

cmdb_find_stale is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cmdb_find_stale": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every cmdb_find_stale call is checked against it from then on.

FAQ

Questions about cmdb_find_stale

What does the cmdb_find_stale tool do? +

Find CIs not updated within a given number of days that are still operational. It is categorised as a Read tool in the ServiceNow MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cmdb_find_stale? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for cmdb_find_stale: 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.

What risk level is cmdb_find_stale? +

cmdb_find_stale is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cmdb_find_stale? +

Yes. Add a rate_limit block to the cmdb_find_stale 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.

How do I block cmdb_find_stale completely? +

Set action: deny in the PolicyLayer policy for cmdb_find_stale. 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.

What MCP server provides cmdb_find_stale? +

cmdb_find_stale 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.

KEEP EXPLORING

More on ServiceNow MCP Server, and thousands of servers like it.

This server

All 415 ServiceNow MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →