Return blog-level metadata: title, subtitle/description, and link.
AI agents call get_blog_info 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 read-only metadata about a blog. It performs a query operation with no side effects, no state changes, and no capability to modify or delete data. It is the lowest-risk category for information discovery on public RSS feeds.
From the tool's definition Tool name 'get_blog_info' and description 'Return blog-level metadata: title, subtitle/description, and link' indicate retrieval of publicly available metadata with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Return blog-level metadata: title, subtitle/description, and link. 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_blog_info: 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_blog_info 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_info 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_info. 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_info 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 →