AUTONOMOUS MULTI-FILE SURGICAL REFACTORING ENGINE Revolutionary capabilities far beyond basic refactoring: - Autonomous multi-file refactoring with dependency graph tracking - Semantic code transplant (move code between files maintaining all refs) - Blast radius analysis before any change - Auto...
Bulk/mass operation — affects multiple targets
Part of the Atlas Pipeline MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke atlas_codebase_surgeon to trigger processes or run actions in Atlas Pipeline. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
atlas_codebase_surgeon can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
atlas_codebase_surgeon:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Atlas Pipeline policy for all 31 tools.
Agents calling execute-class tools like atlas_codebase_surgeon have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
atlas_codebase_surgeon is one of the high-risk operations in Atlas Pipeline. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
AUTONOMOUS MULTI-FILE SURGICAL REFACTORING ENGINE Revolutionary capabilities far beyond basic refactoring: - Autonomous multi-file refactoring with dependency graph tracking - Semantic code transplant (move code between files maintaining all refs) - Blast radius analysis before any change - Auto-rollback generation for every change - Cross-file rename with 100% accuracy - Dead code autopsy and elimination across entire codebase - Interface extraction across entire codebase - Pattern propagation (apply pattern to all similar code) - Dry-run mode for safe testing Use this for surgical precision code modifications that affect multiple files.. It is categorised as a Execute tool in the Atlas Pipeline MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for atlas_codebase_surgeon. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Atlas Pipeline MCP server.
atlas_codebase_surgeon is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the atlas_codebase_surgeon rule in your Intercept 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 Intercept policy for atlas_codebase_surgeon. 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.
atlas_codebase_surgeon is provided by the Atlas Pipeline MCP server (atlas-pipeline-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept