Parses the RSS feed to get a list of all posts.
AI agents call list_blog_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 retrieves and lists blog post metadata from an RSS feed. It performs a read-only query operation with no ability to modify, delete, or execute code. The blast radius of misuse is minimal—at worst, an agent could list posts repeatedly or extract post titles/metadata, neither of which poses security, financial, or destructive risk. It is clearly a Read category tool.
From the tool's definition Tool name 'list_blog_posts' and description 'Parses the RSS feed to get a list of all posts' indicate retrieval of data without modification or side effects.
Attacks that exploit this kind of access
Parses the RSS feed to get a list of all posts. 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 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 Blog RSS MCP Server. Nothing to install.
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 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 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.
list_blog_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 →