snow_blast_radius_field_references
Find every artifact that references a specific table.field across the instance. Use to audit references before changing or removing a field, understand the blast radius of a rename/refactor, or distinguish reads vs writes vs condition uses. Example:
This record as markdown: /tools/serac/snow-blast-radius-field-references.md
What snow_blast_radius_field_references does on Serac
AI agents call snow_blast_radius_field_references 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_field_references is rated Low
This tool retrieves and queries information about field references across a ServiceNow instance. It produces no side effects—it only searches and reports on existing data. While the blast radius insight is valuable for decision-making before destructive actions, the tool itself performs no writes, deletions, or executions. It is purely informational (Read category).
From the tool's definition Tool name and description indicate search/audit functionality: 'Find every artifact that references', 'understand the blast radius', 'audit references'. The verb is 'find' and the purpose is discovery and analysis, not modification.
Attacks that exploit this kind of access
The rule that runs snow_blast_radius_field_references 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_field_references, this is the rule to start with:
snow_blast_radius_field_references 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_field_references call is checked against it from then on.
Questions about snow_blast_radius_field_references
Find every artifact that references a specific table.field across the instance. Use to audit references before changing or removing a field, understand the blast radius of a rename/refactor, or distinguish reads vs writes vs condition uses. Example:. 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_field_references: 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_field_references 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_field_references 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_field_references. 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_field_references 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