neuron_sites_duplicate
Copy a site's live files into a new site with a new address (addresses never change, so this is how to get a different one). No re-upload. The copy starts Restricted with nobody added and goes through review like any new site.
This record as markdown: /tools/io-github-conquext-neuron/neuron-sites-duplicate.md
What neuron_sites_duplicate does on Neuron
AI agents use neuron_sites_duplicate to create or update resources in Neuron, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neuron environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Defaults to 'Copy of <name>'. |
label | string | — | Business plans: the new site's address. Omit to get one generated. |
siteId | string | Yes |
Parameters from the server's own tool schema.
Why neuron_sites_duplicate is rated Medium
An AI agent can call neuron_sites_duplicate faster than any human can review: one bad instruction and it creates or modifies resources in Neuron by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs neuron_sites_duplicate 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_duplicate, this is the rule to start with:
neuron_sites_duplicate stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_sites_duplicate call is checked against it from then on.
Questions about neuron_sites_duplicate
Copy a site's live files into a new site with a new address (addresses never change, so this is how to get a different one). No re-upload. The copy starts Restricted with nobody added and goes through review like any new site. It is categorised as a Write tool in the Neuron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
neuron_sites_duplicate accepts 3 parameters: name, label, siteId. Required: siteId. 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_duplicate: 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_duplicate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the neuron_sites_duplicate 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_duplicate. 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_duplicate 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.
This server
Across the catalogue