Medium Risk

rss_source_save

rss_source_save

How to control rss_source_save ↓

What rss_source_save does on Legado

AI agents use rss_source_save to create or update resources in Legado — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Legado environment.

Medium Risk

Why rss_source_save needs a policy

This tool reversibly creates or updates RSS source configurations within Legado. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). The 'save' operation is characteristic of Write category tools.

From the tool's definition Tool name 'rss_source_save' indicates a save/persist operation on RSS source configuration. Sibling tools on the server include 'book_save' and 'book_save_progress' which are clearly write operations.

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

How to control rss_source_save

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "rss_source_save": {
      "limits": [
        {
          "counter": "rss_source_save_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

rss_source_save stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. 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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about rss_source_save

What does the rss_source_save tool do? +

rss_source_save. It is categorised as a Write tool in the Legado MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rss_source_save? +

Register the Legado MCP server in PolicyLayer and add a rule for rss_source_save: 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_save? +

rss_source_save is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rss_source_save? +

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

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

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