neuron_pull_pool_update
Pull the latest updates for a subscribed pool resource to sync with the publisher's changes. Only applies to items installed with 'subscribe' mode.
This record as markdown: /tools/io-github-conquext-neuron/neuron-pull-pool-update.md
What neuron_pull_pool_update does on Neuron
AI agents use neuron_pull_pool_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 |
|---|---|---|---|
installId | string | Yes | Unique identifier (UUID) of the installed resource to pull updates for |
Parameters from the server's own tool schema.
Why neuron_pull_pool_update is rated Medium
This tool synchronizes local resources with upstream publisher changes, which modifies/updates local data. It is reversible in principle (you can re-pull or roll back) and doesn't delete data, so Write is the most appropriate category. Severity is medium because pulling unexpected or malicious updates could affect bot configurations or campaign behavior at scale across a WhatsApp platform.
From the tool's definition 'Pull the latest updates for a subscribed pool resource to sync with the publisher's changes'
Attacks that exploit this kind of access
The rule that runs neuron_pull_pool_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_pull_pool_update, this is the rule to start with:
neuron_pull_pool_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_pull_pool_update call is checked against it from then on.
Questions about neuron_pull_pool_update
Pull the latest updates for a subscribed pool resource to sync with the publisher's changes. Only applies to items installed with 'subscribe' mode. 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_pull_pool_update accepts 1 parameter: installId. Required: installId. 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_pull_pool_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.
neuron_pull_pool_update 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_pull_pool_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.
Set action: deny in the PolicyLayer policy for neuron_pull_pool_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.
neuron_pull_pool_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.
More on Neuron, and thousands of servers like it.
This server
Across the catalogue