Compute impact radius for changed files. Uses BFS in both directions (callers + callees) to find all impacted code entities. Essential for code review. Args: changed_files: Comma-separated file paths (relative to repo root). max_depth: Maximum BFS depth (default 2). max_nodes: Maximum nodes to re...
AI agents call get_blast_radius to retrieve information from Qualixar/superlocalmemory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is fundamentally a query/analysis tool that retrieves and synthesizes information about code dependencies without side effects. While misuse could lead an agent to make poor refactoring decisions based on incorrect blast radius data, the tool itself only reads the code graph.
From the tool's definition Tool computes and returns impact analysis via BFS traversal of code relationships; description emphasizes 'find all impacted code entities' and 'for code review' (analysis purpose). No modification of files, memory, or code occurs.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access get_blast_radius gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Qualixar/superlocalmemory, and nothing reaches the server without passing your rules. This is the rule we recommend for get_blast_radius:
{
"version": "1",
"default": "deny",
"tools": {
"get_blast_radius": {}
}
}get_blast_radius is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Compute impact radius for changed files. Uses BFS in both directions (callers + callees) to find all impacted code entities. Essential for code review. Args: changed_files: Comma-separated file paths (relative to repo root). max_depth: Maximum BFS depth (default 2). max_nodes: Maximum nodes to return (default 500). It is categorised as a Read tool in the Qualixar/superlocalmemory MCP Server, which means it retrieves data without modifying state.
Register the Qualixar/superlocalmemory MCP server in PolicyLayer and add a rule for get_blast_radius: 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 Qualixar/superlocalmemory. Nothing to install.
get_blast_radius 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 get_blast_radius 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 get_blast_radius. 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.
get_blast_radius is provided by the Qualixar/superlocalmemory MCP server (qualixar/superlocalmemory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 59 Qualixar/superlocalmemory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
59 Qualixar/superlocalmemory tools catalogued and risk-classified — across an index of 42,500+ MCP servers.