get_blog_posts
[MAINTENANCE] Read-only: List workspace-scoped blog posts, newest first. Optional 'status' filter (draft|published|archived). Each post includes a 'url' (/blog/<slug>).
This record as markdown: /tools/io-github-ajc3xc-meridian/get-blog-posts.md
What get_blog_posts does on Meridian
AI agents call get_blog_posts to retrieve information from Meridian 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 |
|---|---|---|---|
status | string | — |
Parameters from the server's own tool schema.
Why get_blog_posts is rated Low
This tool retrieves and queries existing blog posts with no side effects. The 'Read-only' designation and list operation confirm it fits the Read category. Severity is low because the blast radius of misuse is minimal—an agent can only view existing blog post data scoped to the workspace, with no capability to modify, delete, or trigger external actions.
From the tool's definition Tool description explicitly states 'Read-only: List workspace-scoped blog posts' with optional filtering. Returns post metadata including URLs with no modification, creation, or deletion capability.
Attacks that exploit this kind of access
The rule that runs get_blog_posts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meridian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_blog_posts, this is the rule to start with:
get_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 Meridian, apply this rule, and every get_blog_posts call is checked against it from then on.
Questions about get_blog_posts
[MAINTENANCE] Read-only: List workspace-scoped blog posts, newest first. Optional 'status' filter (draft|published|archived). Each post includes a 'url' (/blog/<slug>). It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_blog_posts accepts 1 parameter: status. The full parameter table on this page comes from the server's own tool schema.
Register the Meridian MCP server in PolicyLayer and add a rule for get_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 Meridian. Nothing to install.
get_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 get_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 get_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.
get_blog_posts is provided by the Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meridian, and thousands of servers like it.
This server
Across the catalogue