snow_blast_radius_table_configs
Find every configuration running on a specific table. Use to inventory artifacts scoped to a table, understand the configuration landscape before making changes, or filter by config type, scope, or active status. Example:
This record as markdown: /tools/serac/snow-blast-radius-table-configs.md
What snow_blast_radius_table_configs does on Serac
AI agents call snow_blast_radius_table_configs 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_table_configs is rated Low
This tool retrieves and lists configuration data associated with a specific ServiceNow table. It performs read-only discovery/inventory operations with no stated side effects. Severity is medium because the configuration landscape data it exposes could reveal sensitive architectural details about the ServiceNow instance, aiding reconnaissance if misused.
From the tool's definition Find every configuration running on a specific table... inventory artifacts scoped to a table, understand the configuration landscape before making changes
Attacks that exploit this kind of access
The rule that runs snow_blast_radius_table_configs 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_table_configs, this is the rule to start with:
snow_blast_radius_table_configs 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_table_configs call is checked against it from then on.
Questions about snow_blast_radius_table_configs
Find every configuration running on a specific table. Use to inventory artifacts scoped to a table, understand the configuration landscape before making changes, or filter by config type, scope, or active status. 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_table_configs: 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_table_configs 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_table_configs 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_table_configs. 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_table_configs 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