neuron_list_blog_posts
Retrieve a paginated list of blog posts with optional filtering by status, author type, author ID, or tag.
This record as markdown: /tools/io-github-conquext-neuron/neuron-list-blog-posts.md
What neuron_list_blog_posts does on Neuron
AI agents call neuron_list_blog_posts 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 |
|---|---|---|---|
tag | string | — | Filter posts by tag slug (e.g., 'announcements') |
page | number | — | Page number for pagination (default: 1) |
limit | number | — | Number of results per page (default: 20) |
status | string | — | Filter posts by publication status |
authorId | string | — | Filter posts by author identifier (UUID) |
authorType | string | — | Filter posts by author type |
Parameters from the server's own tool schema.
Why neuron_list_blog_posts is rated Low
This tool retrieves and queries blog post data with no side effects. It returns a paginated list with optional filters but does not create, modify, delete, or execute any operations. It is a straightforward Read operation with minimal risk if misused by an AI agent—the worst outcome would be excessive queries or information disclosure of already-public or accessible blog posts.
From the tool's definition Tool name 'neuron_list_blog_posts' and description 'Retrieve a paginated list of blog posts' indicate a read-only query operation with no modification or deletion capability.
Attacks that exploit this kind of access
The rule that runs neuron_list_blog_posts 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_list_blog_posts, this is the rule to start with:
neuron_list_blog_posts 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_list_blog_posts call is checked against it from then on.
Questions about neuron_list_blog_posts
Retrieve a paginated list of blog posts with optional filtering by status, author type, author ID, or tag. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_list_blog_posts accepts 6 parameters: tag, page, limit, status, authorId, authorType. 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_list_blog_posts: 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_list_blog_posts 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_list_blog_posts 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_list_blog_posts. 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_list_blog_posts 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