Simulate an architectural change before touching any code. Returns health score delta, broken imports, and affected nodes. Zero file I/O \u2014 pure in-memory simulation. Cross-language edges included \u2014 deleting a Python route file will show TypeScript callers as affected. Operations: - dele...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Depwire Cli server.
Free to start. No card required.
AI agents may call simulate_change to permanently remove or destroy resources in Depwire Cli. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call simulate_change in a loop, permanently destroying resources in Depwire Cli. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"simulate_change"
]
}See the full Depwire Cli policy for all 23 tools.
These attack patterns abuse exactly the kind of access simulate_change gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Simulate an architectural change before touching any code. Returns health score delta, broken imports, and affected nodes. Zero file I/O \u2014 pure in-memory simulation. Cross-language edges included \u2014 deleting a Python route file will show TypeScript callers as affected. Operations: - delete: Simulate deleting a file. Shows every file that would break and the full blast radius. - move: Simulate moving a file to a new path. Shows broken imports and edge changes. - rename: Simulate renaming a file. Shows all affected imports and nodes. - split: Simulate splitting a file by moving specified symbols to a new file. - merge: Simulate merging two files into one. Fails fast on symbol name collision. Always run this before any refactor that touches file structure.. It is categorised as a Destructive tool in the Depwire Cli MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Depwire Cli MCP server in PolicyLayer and add a rule for simulate_change: 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 Depwire Cli. Nothing to install.
simulate_change is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the simulate_change 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 simulate_change. 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.
simulate_change is provided by the Depwire Cli MCP server (depwire-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 23 Depwire Cli tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.