neuron_sites_publish
Publish a static site (HTML/CSS/JS/images/fonts/PDF/video) and get its link. Creates a new site when siteId is omitted, otherwise redeploys to the same URL — the link and access settings survive and the previous version stays available for rollback. Pass exactly one source: dir (local folder, e.g...
This record as markdown: /tools/io-github-conquext-neuron/neuron-sites-publish.md
What neuron_sites_publish does on Neuron
AI agents use neuron_sites_publish 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 |
|---|---|---|---|
dir | string | — | Local folder to publish (local MCP only). index.html at its root opens first. |
html | string | — | A single HTML page; becomes index.html. |
mode | string | — | 'replace' (default): the source IS the whole site. 'patch' (needs siteId): start from the live version; the source's files add/replace those paths, `delete` rem |
name | string | — | Name for a new site (required when siteId is omitted). |
note | string | — | Version note, e.g. 'Added pack 41'. |
files | array | — | Files as base64 with relative paths. |
label | string | — | Business plans: the address for a new site (<label>.<sites domain>). Lowercase letters, numbers, hyphens. Can't be changed later. Omit to get one generated. |
delete | array | — | mode=patch only: site paths to remove, e.g. ['brand/old-logo.png']. |
siteId | string | — | Existing site to redeploy. Omit to create a new site. |
zipPath | string | — | Local .zip to publish (local MCP only). A single top-level folder is unwrapped. |
entryPath | string | — | Page that opens at / when there's no index.html. |
Parameters from the server's own tool schema.
Why neuron_sites_publish is rated Medium
An AI agent can call neuron_sites_publish 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.
Risk signalsAccepts file system path (dir) · Accepts raw HTML/template content (html) · High parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs neuron_sites_publish 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_publish, this is the rule to start with:
neuron_sites_publish 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_publish call is checked against it from then on.
Questions about neuron_sites_publish
Publish a static site (HTML/CSS/JS/images/fonts/PDF/video) and get its link. Creates a new site when siteId is omitted, otherwise redeploys to the same URL — the link and access settings survive and the previous version stays available for rollback. Pass exactly one source: dir (local folder, e.g. the output of a build), zipPath (local .zip), html (a single page), or files ([{path, base64}]). New sites start Restricted (only you). Use neuron_sites_set_access to share. Only changed files are uploaded on redeploy. A new site is reviewed by Neuron once; until approved (reviewStatus), visitors can't open it. Its address (label) is fixed for life. 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_publish accepts 11 parameters: dir, html, mode, name, note, files, label, delete, siteId, zipPath, entryPath. 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_publish: 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_publish 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_publish 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_publish. 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_publish 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