Low Risk

rss_source_debug

Debug an RSS source and return logs in one go.

How to control rss_source_debug ↓

What rss_source_debug does on Legado

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

Low Risk

Why rss_source_debug needs a policy

This tool retrieves and returns diagnostic information (logs) about an RSS source. It is a read-only operation that queries state without creating, modifying, deleting, or executing arbitrary operations. The lower severity reflects that accessing debug logs poses minimal risk—it only exposes diagnostic data about an existing RSS source.

From the tool's definition The tool 'rss_source_debug' performs debugging of an RSS source and returns logs. The verb 'debug' and the return of 'logs' indicate information retrieval and diagnostic operations without modification or execution of external code.

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

How to control rss_source_debug

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

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

rss_source_debug 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 Legado — 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 rss_source_debug

What does the rss_source_debug tool do? +

Debug an RSS source and return logs in one go. It is categorised as a Read tool in the Legado MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on rss_source_debug? +

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

What risk level is rss_source_debug? +

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

Can I rate-limit rss_source_debug? +

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

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

rss_source_debug is provided by the Legado MCP server (joestar817/legado-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 Legado tool call.

Start from Legado, 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.

31 Legado 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.