Low Risk

get_unread_items

get_unread_items

How to control get_unread_items ↓

What get_unread_items does on RSS MCP Server

AI agents call get_unread_items to retrieve information from RSS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_unread_items needs a policy

This tool retrieves unread items from an RSS feed system, which is a read-only query operation with no side effects. The empty description and naming pattern consistent with other read operations (get_*) confirm it performs data retrieval without modifying state. Low severity because unauthorized access retrieves only feed metadata/content, not sensitive system operations.

From the tool's definition Tool name 'get_unread_items' combined with sibling tools 'get_feeds', 'get_groups', 'get_items', and 'get_saved_items' all indicate retrieval operations. The server description explicitly states 'retrieval of feeds, groups, and items' as a primary capability.

Documented attack patterns abuse exactly the kind of access get_unread_items gives an agent:

How to control get_unread_items

PolicyLayer is an MCP gateway — it sits between your AI agents and RSS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_unread_items:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_unread_items": {}
  }
}

get_unread_items is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register RSS MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_unread_items

What does the get_unread_items tool do? +

get_unread_items. It is categorised as a Read tool in the RSS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_unread_items? +

Register the RSS MCP Server MCP server in PolicyLayer and add a rule for get_unread_items: 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 RSS MCP Server. Nothing to install.

What risk level is get_unread_items? +

get_unread_items is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_unread_items? +

Yes. Add a rate_limit block to the get_unread_items 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.

How do I block get_unread_items completely? +

Set action: deny in the PolicyLayer policy for get_unread_items. 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.

What MCP server provides get_unread_items? +

get_unread_items is provided by the RSS MCP Server MCP server (weekend-project-space/rss-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every RSS MCP Server tool call.

Start from RSS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

8 RSS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.