cmdb_health_dashboard

Get CMDB data quality metrics (completeness of server and network CI data)

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-health-dashboard.md

WHAT IT DOES

What cmdb_health_dashboard does on ServiceNow MCP Server

AI agents call cmdb_health_dashboard 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_health_dashboard is rated Low

This tool queries and retrieves data from the Configuration Management Database (CMDB) to provide health and quality metrics. It has no write, execute, destructive, or financial capabilities. The blast radius of misuse is minimal — an AI agent could at worst access information about CMDB data quality, which is read-only operational metadata. No data is created, modified, deleted, or acted upon.

From the tool's definition Tool description explicitly states "Get CMDB data quality metrics" — a retrieval operation with no mutation or side effects. Returns metrics about data completeness.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

cmdb_health_dashboard Allowed

cmdb_health_dashboard 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_health_dashboard": {}
  }
}

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_health_dashboard call is checked against it from then on.

FAQ

Questions about cmdb_health_dashboard

What does the cmdb_health_dashboard tool do? +

Get CMDB data quality metrics (completeness of server and network CI data). 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_health_dashboard? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for cmdb_health_dashboard: 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_health_dashboard? +

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

Can I rate-limit cmdb_health_dashboard? +

Yes. Add a rate_limit block to the cmdb_health_dashboard 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_health_dashboard completely? +

Set action: deny in the PolicyLayer policy for cmdb_health_dashboard. 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_health_dashboard? +

cmdb_health_dashboard 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 365 ServiceNow MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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