neuron_get_collection_items
Browse the mined content in a collection — posts/comments/profiles with author, content, engagement and engagementScore. sort 'top' ranks by engagement (great for picking the best clips/posts to reuse or distill into a persona).
This record as markdown: /tools/io-github-conquext-neuron/neuron-get-collection-items.md
What neuron_get_collection_items does on Neuron
AI agents call neuron_get_collection_items 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | — | |
sort | string | — | top = highest engagement first (default recent). |
type | string | — | Filter by item type (post|comment|profile|page|custom). |
limit | integer | — | |
collectionId | string | Yes | The collection id. |
Parameters from the server's own tool schema.
Why neuron_get_collection_items is rated Low
Even though neuron_get_collection_items 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.
Attacks that exploit this kind of access
The rule that runs neuron_get_collection_items 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_collection_items, this is the rule to start with:
neuron_get_collection_items 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_collection_items call is checked against it from then on.
Questions about neuron_get_collection_items
Browse the mined content in a collection — posts/comments/profiles with author, content, engagement and engagementScore. sort 'top' ranks by engagement (great for picking the best clips/posts to reuse or distill into a persona). It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_get_collection_items accepts 5 parameters: page, sort, type, limit, collectionId. Required: collectionId. 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_get_collection_items: 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_collection_items 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_collection_items 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_collection_items. 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_collection_items 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