blast_radius_table_configs
Blast radius (config/metadata impact, not CMDB CI impact): list every configuration artifact scoped to a table (business rules, client scripts, UI policies, ACLs, UI actions, data policies, dictionary fields), with per-type counts. Run before altering or removing a table. Each lane returns {count...
This record as markdown: /tools/servicenow-mcp-server/blast-radius-table-configs.md
What blast_radius_table_configs does on ServiceNow MCP Server
AI agents call blast_radius_table_configs to retrieve information from ServiceNow MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why blast_radius_table_configs is rated Low
This tool reads and retrieves configuration metadata about a table — it lists artifacts and counts without modifying anything. However, severity is medium because the information it exposes (ACLs, business rules, dictionary fields) is sensitive security-relevant metadata that could be used to plan destructive or exploitative actions against the ServiceNow instance.
From the tool's definition list every configuration artifact scoped to a table (business rules, client scripts, UI policies, ACLs, UI actions, data policies, dictionary fields), with per-type counts
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs blast_radius_table_configs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blast_radius_table_configs, this is the rule to start with:
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 ServiceNow MCP Server, apply this rule, and every blast_radius_table_configs call is checked against it from then on.
Questions about blast_radius_table_configs
Blast radius (config/metadata impact, not CMDB CI impact): list every configuration artifact scoped to a table (business rules, client scripts, UI policies, ACLs, UI actions, data policies, dictionary fields), with per-type counts. Run before altering or removing a table. Each lane returns {count, records} or {error} if that table/plugin is unavailable. It is categorised as a Read tool in the ServiceNow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for 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 ServiceNow MCP Server. Nothing to install.
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 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 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.
blast_radius_table_configs is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
This server
Across the catalogue