neuron_sites_update

SERVERNeuron SOURCEneuron-mcp-server

Medium RISK CLASS

Category Write

Parameters 61 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-conquext-neuron/neuron-sites-update.md

WHAT IT DOES

What neuron_sites_update does on Neuron

AI agents use neuron_sites_update 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	—
`siteId`	string	Yes
`cspMode`	string	—	'strict' (default: same-origin only) or 'external' (also allow https: scripts/styles/images/fonts). Forms and outbound fetches stay blocked either way.
`entryPath`	string	—
`notifyEmail`	boolean	—	Email org owners/admins about access requests
`previewFromPage`	boolean	—	Link previews (WhatsApp, X, Slack…) show the entry page's own title and description instead of just the site name and who shared it. Visible to anyone holding t

Parameters from the server's own tool schema.

RISK

Why neuron_sites_update is rated Medium

An AI agent can call neuron_sites_update 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

RECOMMENDED RULE

The rule that runs neuron_sites_update 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_update, this is the rule to start with:

neuron_sites_update Rate-limited

neuron_sites_update 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "neuron_sites_update": {
      "limits": [
        {
          "counter": "neuron_sites_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_sites_update call is checked against it from then on.

FAQ

Questions about neuron_sites_update

What does the neuron_sites_update tool do? +

Rename a site, change its entry page, toggle owner email alerts, allow external resources (CDN scripts/styles/images over https), or choose what link previews show. Content changes go through neuron_sites_publish. 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.

What parameters does neuron_sites_update accept? +

neuron_sites_update accepts 6 parameters: name, siteId, cspMode, entryPath, notifyEmail, previewFromPage. Required: siteId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on neuron_sites_update? +

Register the Neuron MCP server in PolicyLayer and add a rule for neuron_sites_update: 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.

What risk level is neuron_sites_update? +

neuron_sites_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit neuron_sites_update? +

Yes. Add a rate_limit block to the neuron_sites_update 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.

How do I block neuron_sites_update completely? +

Set action: deny in the PolicyLayer policy for neuron_sites_update. 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.

What MCP server provides neuron_sites_update? +

neuron_sites_update 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.

KEEP EXPLORING

More on Neuron, and thousands of servers like it.

This server

All 401 Neuron tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →