neuron_get_flow_catalog
Retrieve the COMPLETE catalog for authoring flows. ALWAYS call this first when building or editing a flow — do not rely on memory, the full node set changes. The response has two parts: • data: every node type (all triggers, logic, and actions) with its config fields (including options enums and ...
This record as markdown: /tools/io-github-conquext-neuron/neuron-get-flow-catalog.md
What neuron_get_flow_catalog does on Neuron
AI agents call neuron_get_flow_catalog to retrieve information from Neuron without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why neuron_get_flow_catalog is rated Low
Even though neuron_get_flow_catalog only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs neuron_get_flow_catalog 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_get_flow_catalog, this is the rule to start with:
neuron_get_flow_catalog is read-only, so it stays allowed. 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_get_flow_catalog call is checked against it from then on.
Questions about neuron_get_flow_catalog
Retrieve the COMPLETE catalog for authoring flows. ALWAYS call this first when building or editing a flow — do not rely on memory, the full node set changes. The response has two parts: • data: every node type (all triggers, logic, and actions) with its config fields (including options enums and required), output handles, and dynamicHandles. • reference: the authoring guide you need for anything non-trivial — - conditions: the ConditionGroup JSON shape + the full operator vocabulary (used by branch/filter/switch/loop and trigger filters). Note: on LOGIC nodes a rule's field is a {{template}}; on a TRIGGER's config.conditions it is a raw payload path. - compositeFields: the exact JSON for field kinds the flat schema can't express — cases (switch), assignments (set_fields), weekdays, and the delay amount/unit note. - triggerConditions: every trigger also accepts an optional config.conditions AND/OR filter over the raw event payload. - templating, errorHandling (__errorHandling), handles (wiring map), and examples (simple, branching AND/OR, and complex switch+set_fields+expression graphs to imitate). The catalog is grouped by kind: trigger (entry points), logic (routing/waits/data), action (side effects). There are dozens of node types — read data for the authoritative list rather than assuming. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
Register the Neuron MCP server in PolicyLayer and add a rule for neuron_get_flow_catalog: 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_get_flow_catalog is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the neuron_get_flow_catalog 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_get_flow_catalog. 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_get_flow_catalog 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