Low Risk

get_all_entries

get_all_entries

How to control get_all_entries ↓

What get_all_entries does on RSS MCP Server

AI agents call get_all_entries 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_all_entries needs a policy

This tool retrieves RSS feed entries without modifying, deleting, or executing operations. The name and context suggest it fetches all entries from an RSS reader—a read operation with no destructive or state-changing effects. Although the description is empty, the naming convention and sibling tool patterns provide sufficient confidence in the Read classification.

From the tool's definition Tool is named `get_all_entries` and follows the read-query pattern of sibling tools like `freshapi_get_stream_item_ids` and `freshapi_get_stream_item_contents`, which retrieve feed data.

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

How to control get_all_entries

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

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

get_all_entries 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_all_entries

What does the get_all_entries tool do? +

get_all_entries. 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_all_entries? +

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

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

Can I rate-limit get_all_entries? +

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

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

get_all_entries is provided by the RSS MCP Server MCP server (xueli-sherryli/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.

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