snow_blast_radius_artifact_dependencies
Forward dependency analysis for a single artifact: what does it read, write, and depend on? Use to understand what fields a business rule touches, what tables a script include queries, which script includes an artifact calls, and the artifact
This record as markdown: /tools/serac/snow-blast-radius-artifact-dependencies.md
What snow_blast_radius_artifact_dependencies does on Serac
AI agents call snow_blast_radius_artifact_dependencies 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_blast_radius_artifact_dependencies is rated Low
The tool performs static analysis and dependency mapping of a ServiceNow artifact — it reads and reports on what fields, tables, and script includes an artifact references. It does not modify, execute, or delete anything. Severity is medium because dependency graphs of production artifacts can expose sensitive architectural details about business logic and data flows.
From the tool's definition Forward dependency analysis for a single artifact: what does it read, write, and depend on?
Attacks that exploit this kind of access
The rule that runs snow_blast_radius_artifact_dependencies 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_blast_radius_artifact_dependencies, this is the rule to start with:
snow_blast_radius_artifact_dependencies 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_blast_radius_artifact_dependencies call is checked against it from then on.
Questions about snow_blast_radius_artifact_dependencies
Forward dependency analysis for a single artifact: what does it read, write, and depend on? Use to understand what fields a business rule touches, what tables a script include queries, which script includes an artifact calls, and the artifact. 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_blast_radius_artifact_dependencies: 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_blast_radius_artifact_dependencies 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_blast_radius_artifact_dependencies 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_blast_radius_artifact_dependencies. 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_blast_radius_artifact_dependencies 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