Browse articles with pagination and filtering. Returns latest articles first (by pubDate DESC). Use for: checking recent articles, browsing unread items, filtering by status/source/date. Token-efficient: returns ONLY titles + metadata by default. Add includeExcerpt for previews or includeContent ...
AI agents call get_content to retrieve information from MCP RSS without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query and retrieval tool for RSS feed data. It allows browsing, filtering, and fetching article content with various optional parameters, but performs no modifications to data, executes no external operations, and has no destructive or financial implications. The 'token-efficient' design and pagination features confirm it is read-only data retrieval.
From the tool's definition Tool description explicitly states 'Browse articles' and 'Returns latest articles first'; enables 'checking recent articles, browsing unread items, filtering by status/source/date'; returns 'ONLY titles + metadata by default' with optional content retrieval.
Attacks that exploit this kind of access
Browse articles with pagination and filtering. Returns latest articles first (by pubDate DESC). Use for: checking recent articles, browsing unread items, filtering by status/source/date. Token-efficient: returns ONLY titles + metadata by default. Add includeExcerpt for previews or includeContent for full text. Supports: multi-status filtering, date ranges, favorite blog prioritization. Response includes total count for pagination. It is categorised as a Read tool in the MCP RSS MCP Server, which means it retrieves data without modifying state.
Register the MCP RSS MCP server in PolicyLayer and add a rule for get_content: 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 MCP RSS. Nothing to install.
get_content 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_content 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_content. 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_content is provided by the MCP RSS MCP server (ronnycoding/my_mcp_rss). 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 →