snow_diagnose_setup
Diagnose the ServiceNow connection: which credential source was used (environment variables, auth.json, enterprise portal), whether the instance URL is well-formed, whether the instance is awake or hibernating, whether the OAuth token exchange succeeds, and which roles the authenticated account h...
This record as markdown: /tools/serac/snow-diagnose-setup.md
What snow_diagnose_setup does on Serac
AI agents use snow_diagnose_setup to create or update resources in Serac, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Serac environment.
Why snow_diagnose_setup is rated Medium
An AI agent can call snow_diagnose_setup faster than any human can review: one bad instruction and it creates or modifies resources in Serac by the hundred, each call as confident as the last.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs snow_diagnose_setup 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_diagnose_setup, this is the rule to start with:
snow_diagnose_setup stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_diagnose_setup call is checked against it from then on.
Questions about snow_diagnose_setup
Diagnose the ServiceNow connection: which credential source was used (environment variables, auth.json, enterprise portal), whether the instance URL is well-formed, whether the instance is awake or hibernating, whether the OAuth token exchange succeeds, and which roles the authenticated account holds. Call this when a tool fails with an authentication error, a 401, or a response that will not parse as JSON — a hibernating developer instance answers with an HTML login page, and every tool then looks like it has a parse bug. Returns a report naming the broken link and what to do about it. It is categorised as a Write tool in the Serac MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Serac MCP server in PolicyLayer and add a rule for snow_diagnose_setup: 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_diagnose_setup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the snow_diagnose_setup 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_diagnose_setup. 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_diagnose_setup 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