neuron_sites_set_access

SERVERNeuron SOURCEneuron-mcp-server

Medium RISK CLASS

Category Write

Parameters 121 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-set-access.md

WHAT IT DOES

What neuron_sites_set_access does on Neuron

AI agents use neuron_sites_set_access 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
`paused`	boolean	—	Pause: everyone but owners sees 'not available'. Files are kept.
`siteId`	string	Yes
`password`	string \| null	—	Set (8–128 chars) or null to remove. Changing it logs everyone out.
`addPeople`	array	—
`rotateLink`	boolean	—
`allowReshare`	boolean	—
`confirmPublic`	boolean	—	Required to switch to 'public'.
`generalAccess`	string	—
`linkExpiresAt`	string \| null	—	ISO datetime when the link stops working, or null
`allowedDomains`	array	—	For 'domain' mode, e.g. ['letschop.io']
`peopleExpireAt`	string \| null	—	ISO datetime when access for addPeople ends
`removeGrantIds`	array	—	Grant ids from neuron_sites_get → people

Parameters from the server's own tool schema.

RISK

Why neuron_sites_set_access is rated Medium

An AI agent can call neuron_sites_set_access 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 signalsHandles credentials or secrets (password) · High parameter count (16 properties) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

neuron_sites_set_access Rate-limited

neuron_sites_set_access 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_set_access": {
      "limits": [
        {
          "counter": "neuron_sites_set_access_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_set_access call is checked against it from then on.

FAQ

Questions about neuron_sites_set_access

What does the neuron_sites_set_access tool do? +

Control who can open a site, Google Docs style. generalAccess: 'restricted' (only named people), 'link' (anyone with the unguessable link), 'request' (anyone can ask; you approve), 'org' (members of your Neuron org), 'domain' (verified emails on allowedDomains), 'public' (anyone — requires confirmPublic). Optionally add a password (applies to everyone but owners), add/remove named people (email / WhatsApp number / Neuron user id, with optional expiry), rotate the link (old link dies instantly), set a link expiry, or pause the site. Every change logs current viewers out within ~15 seconds. 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_set_access accept? +

neuron_sites_set_access accepts 12 parameters: paused, siteId, password, addPeople, rotateLink, allowReshare, confirmPublic, generalAccess, linkExpiresAt, allowedDomains, peopleExpireAt, removeGrantIds. 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_set_access? +

Register the Neuron MCP server in PolicyLayer and add a rule for neuron_sites_set_access: 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_set_access? +

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

Can I rate-limit neuron_sites_set_access? +

Yes. Add a rate_limit block to the neuron_sites_set_access 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_set_access completely? +

Set action: deny in the PolicyLayer policy for neuron_sites_set_access. 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_set_access? +

neuron_sites_set_access 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

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server → The MCP Attack Database →

Guides

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