neuron_sites_delete
Permanently wipe a site: every version, its files in storage, people, access requests and view history. The address stops working. Cannot be undone or recovered. Use neuron_sites_set_access {paused:true} to take it down temporarily instead.
This record as markdown: /tools/io-github-conquext-neuron/neuron-sites-delete.md
What neuron_sites_delete does on Neuron
AI agents call neuron_sites_delete to permanently remove resources in Neuron, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
siteId | string | Yes | |
confirm | boolean | Yes | Must be true |
Parameters from the server's own tool schema.
Why neuron_sites_delete is rated Critical
An AI agent that decides to call neuron_sites_delete doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Neuron is gone. There is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs neuron_sites_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Neuron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For neuron_sites_delete, this is the rule to start with:
neuron_sites_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_sites_delete call is checked against it from then on.
Questions about neuron_sites_delete
Permanently wipe a site: every version, its files in storage, people, access requests and view history. The address stops working. Cannot be undone or recovered. Use neuron_sites_set_access {paused:true} to take it down temporarily instead. It is categorised as a Destructive tool in the Neuron MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
neuron_sites_delete accepts 2 parameters: siteId, confirm. Required: siteId, confirm. The full parameter table on this page comes from the server's own tool schema.
Register the Neuron MCP server in PolicyLayer and add a rule for neuron_sites_delete: 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 Neuron. Nothing to install.
neuron_sites_delete 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 neuron_sites_delete 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 neuron_sites_delete. 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.
neuron_sites_delete is provided by the Neuron MCP server (neuron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Neuron, and thousands of servers like it.
Across the catalogue