neuron_create_blog_post
Create a new blog post. Body can be authored two ways: (1) content as markdown (GFM) + inline raw HTML, or (2) blocks — a structured array of typed layout blocks rendered as styled components (heroes, columns, callouts, code cards, embeds, CTAs, sanitized custom HTML). Prefer blocks for rich, mag...
This record as markdown: /tools/io-github-conquext-neuron/neuron-create-blog-post.md
What neuron_create_blog_post does on Neuron
AI agents use neuron_create_blog_post 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 |
|---|---|---|---|
tags | array | — | List of tag names or slugs to categorize the post |
title | string | Yes | Title of the blog post (max 500 characters) |
blocks | array | — | Structured layout blocks, rendered top-to-bottom as styled components. Each block is an object with a `type` and its fields: - hero: { type:'hero', title, kicke |
status | string | — | Initial publication status of the post (default: 'draft') |
content | string | — | Optional markdown body (GFM + inline raw HTML). Used when `blocks` is not provided, and kept as a fallback when it is. Rich options: , <video src con |
excerpt | string | — | Short summary or preview text for the blog post |
seoTitle | string | — | Custom SEO title override for search engine results |
authorType | string | Yes | Whether the post is authored by an individual user or the organization |
seoKeywords | array | — | List of SEO keywords for search engine optimization |
coverImageUrl | string | — | URL of the cover image displayed at the top of the post |
seoDescription | string | — | Meta description for search engine result snippets |
Parameters from the server's own tool schema.
Why neuron_create_blog_post is rated Medium
An AI agent can call neuron_create_blog_post faster than any human can review: one bad instruction and it creates or modifies resources in Neuron by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (content) · High parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs neuron_create_blog_post 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_create_blog_post, this is the rule to start with:
neuron_create_blog_post 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_create_blog_post call is checked against it from then on.
Questions about neuron_create_blog_post
Create a new blog post. Body can be authored two ways: (1) content as markdown (GFM) + inline raw HTML, or (2) blocks — a structured array of typed layout blocks rendered as styled components (heroes, columns, callouts, code cards, embeds, CTAs, sanitized custom HTML). Prefer blocks for rich, magazine-style layouts; use content for simple prose. If both are given, blocks renders and content is kept as a fallback. 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_create_blog_post accepts 11 parameters: tags, title, blocks, status, content, excerpt, seoTitle, authorType, seoKeywords, coverImageUrl, seoDescription. Required: title, 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_create_blog_post: 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_create_blog_post 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_create_blog_post 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_create_blog_post. 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_create_blog_post 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