get_feeds

THE RISK

Low Risk

Why get_feeds needs a policy

This tool only retrieves feed data from the API without making any changes, creating side effects, or executing external operations. It is a straightforward read operation that queries and returns existing data.

From the tool's definition Tool name 'get_feeds' and description 'Fetch all feeds from the Fever API' indicate a retrieval operation with no modification or deletion of data.

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

POLICY

How to control get_feeds

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_feeds:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_feeds": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More RSS MCP Server tools

Write mark_item Mark an RSS item with a specific action via the Fever API. Read get_groups Fetch all feed groups from the Fever API. Read get_items Fetch RSS items from the Fever API since a given item ID. Read get_items_by_feed_ids get_items_by_feed_ids Read get_items_by_group_ids get_items_by_group_ids Read get_saved_items Fetch saved (favorited) RSS items from the Fever API. Read get_unread_items get_unread_items

All 8 RSS MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_feeds

What does the get_feeds tool do? +

Fetch all feeds from the Fever API. 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_feeds? +

Register the RSS MCP Server MCP server in PolicyLayer and add a rule for get_feeds: 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_feeds? +

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

Can I rate-limit get_feeds? +

Yes. Add a rate_limit block to the get_feeds 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_feeds completely? +

Set action: deny in the PolicyLayer policy for get_feeds. 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_feeds? +

get_feeds 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.

CHECK YOUR STACK →