neuron_install_from_pool
Install a resource from the marketplace pool into the current organization. Choose 'fork' for an independent copy or 'subscribe' to receive future updates from the publisher.
This record as markdown: /tools/io-github-conquext-neuron/neuron-install-from-pool.md
What neuron_install_from_pool does on Neuron
AI agents use neuron_install_from_pool 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 |
|---|---|---|---|
id | string | Yes | Unique identifier (UUID) of the pool item to install |
mode | string | — | Installation mode: 'fork' creates an independent copy, 'subscribe' links to publisher updates (default: 'fork') |
Parameters from the server's own tool schema.
Why neuron_install_from_pool is rated Medium
This tool creates new resources in an organization and modifies organizational state (adding marketplace items, creating forks, or subscribing to updates). It is reversible (resources can be uninstalled) and does not delete data, execute arbitrary code, or transfer funds, making it a Write operation.
From the tool's definition Tool name contains 'install' and description states 'Install a resource from the marketplace pool into the current organization' with options to 'fork' (create copy) or 'subscribe' (establish ongoing relationship).
Attacks that exploit this kind of access
The rule that runs neuron_install_from_pool 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_install_from_pool, this is the rule to start with:
neuron_install_from_pool 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_install_from_pool call is checked against it from then on.
Questions about neuron_install_from_pool
Install a resource from the marketplace pool into the current organization. Choose 'fork' for an independent copy or 'subscribe' to receive future updates from the publisher. 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_install_from_pool accepts 2 parameters: id, mode. Required: id. 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_install_from_pool: 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_install_from_pool 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_install_from_pool 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_install_from_pool. 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_install_from_pool 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