get_integration_health
Report the health of Vulnerability Response data integration runs (sn_vul_integration_run) over a recent window. Surfaces failed runs and — critically — silent stalls where no runs occurred at all (e.g. an NVD/Qualys feed quietly failing with 503/429). Returns success/failure counts, the most rec...
This record as markdown: /tools/tedorigawa001-servicenow-mcp/get-integration-health.md
What get_integration_health does on ServiceNow-MCP
AI agents call get_integration_health to retrieve information from ServiceNow-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_integration_health is rated Low
This tool queries and reports on the status of integration runs. It retrieves historical data about past integration execution (counts, timestamps, details) and surfaces alerts. There is no modification, deletion, execution of external commands, or financial impact. The retrieval of integration health metrics and diagnostic information is a read-only operation typical of monitoring and observability tools.
From the tool's definition Tool description states it 'Report[s] the health' and 'Returns success/failure counts, the most recent success and failure timestamps, recent run details, and actionable alerts' — purely retrieving and surfacing monitoring/status data with no side effects.
Attacks that exploit this kind of access
The rule that runs get_integration_health safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_integration_health, this is the rule to start with:
get_integration_health is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every get_integration_health call is checked against it from then on.
Questions about get_integration_health
Report the health of Vulnerability Response data integration runs (sn_vul_integration_run) over a recent window. Surfaces failed runs and — critically — silent stalls where no runs occurred at all (e.g. an NVD/Qualys feed quietly failing with 503/429). Returns success/failure counts, the most recent success and failure timestamps, recent run details, and actionable alerts. It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow MCP server in PolicyLayer and add a rule for get_integration_health: 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. Nothing to install.
get_integration_health 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 get_integration_health 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 get_integration_health. 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.
get_integration_health is provided by the ServiceNow MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow, and thousands of servers like it.
This server
Across the catalogue