Return the most recent count posts (by published date).
AI agents call get_recent_posts to retrieve information from Blog RSS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing blog post data without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that fetches metadata about blog posts ordered by recency. No data is changed, no external code is executed, and no financial transactions occur.
From the tool's definition Tool returns recent posts by published date with no parameters allowing modification or deletion. The server description emphasizes 'enables interaction with blog RSS/Atom feeds to list posts, fetch content' and this tool retrieves posts 'by published date'…
Attacks that exploit this kind of access
Return the most recent count posts (by published date). It is categorised as a Read tool in the Blog RSS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Blog RSS MCP Server MCP server in PolicyLayer and add a rule for get_recent_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 Blog RSS MCP Server. Nothing to install.
get_recent_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_recent_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_recent_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_recent_posts is provided by the Blog RSS MCP Server MCP server (s1r15h/blog-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →