Return the full structured content of a single Nextdev customer blog post. Returns the title, excerpt, category, post type, tags, plus the complete content as an ordered array of typed blocks: code blocks (with language tag), comparison blocks (left/right vendor columns), step blocks, table block...
AI agents call get_blog_post to retrieve information from Nextdev MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns existing blog post data in a structured format. It has no side effects—it does not create, modify, delete, or execute any operations. It is a straightforward data retrieval operation, fitting squarely within the Read category.
From the tool's definition Tool returns the 'full structured content' of blog posts with 'title, excerpt, category, post type, tags, plus the complete content' delivered as 'an ordered array of typed blocks.' The description explicitly states 'agents read blocks' and positions this as…
Documented attack patterns abuse exactly the kind of access get_blog_post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nextdev MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_blog_post:
{
"version": "1",
"default": "deny",
"tools": {
"get_blog_post": {}
}
}get_blog_post is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Return the full structured content of a single Nextdev customer blog post. Returns the title, excerpt, category, post type, tags, plus the complete content as an ordered array of typed blocks: code blocks (with language tag), comparison blocks (left/right vendor columns), step blocks, table blocks, list blocks, company-card blocks, headings, quotes, callouts, text. This is the structured artifact behind the post — agents read blocks, not HTML. Use this AFTER query_blog identifies a post worth fully reading. It is categorised as a Read tool in the Nextdev MCP MCP Server, which means it retrieves data without modifying state.
Register the Nextdev MCP server in PolicyLayer and add a rule for get_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 Nextdev MCP. Nothing to install.
get_blog_post 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 get_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 get_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.
get_blog_post is provided by the Nextdev MCP server (nextdev-labs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Nextdev MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Nextdev MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.