This record as markdown: /tools/serac/snow-check-health.md
What snow_check_health does on Serac
AI agents call snow_check_health to retrieve information from Serac without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why snow_check_health is rated Low
This tool performs a diagnostic read of system health status. It retrieves information about the ServiceNow instance state (uptime, component status, performance metrics, etc.) with no side effects, data modification, or execution of external operations. This is a standard monitoring/observability operation that poses minimal risk even if called by an autonomous agent.
From the tool's definition Tool name 'snow_check_health' and description 'Check ServiceNow instance health' indicate a query/status check operation that retrieves health metrics or status information without modifying or executing operations.
Attacks that exploit this kind of access
The rule that runs snow_check_health safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_check_health, this is the rule to start with:
snow_check_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 Serac, apply this rule, and every snow_check_health call is checked against it from then on.
Questions about snow_check_health
Check ServiceNow instance health. It is categorised as a Read tool in the Serac MCP Server, which means it retrieves data without modifying state.
Register the Serac MCP server in PolicyLayer and add a rule for snow_check_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 Serac. Nothing to install.
snow_check_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 snow_check_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 snow_check_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.
snow_check_health is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Serac, and thousands of servers like it.
This server
Across the catalogue