batch_edit_subscriptions · Inoreader MCP: Risk & Policy

WHAT IT DOES

What batch_edit_subscriptions does on Inoreader

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

WHY IT NEEDS A POLICY

Why batch_edit_subscriptions needs a policy

This tool modifies feed subscription metadata (folder assignments) without deleting data. The changes are reversible — feeds can be moved to different folders or uncategorized. While affecting multiple subscriptions in batch, the impact is non-destructive and scoped to feed organization. Severity is medium due to potential for confusion if subscriptions are organized incorrectly, but this is remediable.

From the tool's definition Tool description states 'Add multiple feeds to folders' — a direct modification of subscription organization.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_edit_subscriptions Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "batch_edit_subscriptions": {
      "limits": [
        {
          "counter": "batch_edit_subscriptions_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Inoreader, so you can run agents against it safely.

FAQ

Questions about batch_edit_subscriptions

What does the batch_edit_subscriptions tool do? +

Deprecated: use categorize_feeds instead (more reliable, folder-centric input). Add multiple feeds to folders. Each edit costs 1 Zone 2 request. It is categorised as a Write tool in the Inoreader MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on batch_edit_subscriptions? +

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

What risk level is batch_edit_subscriptions? +

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

Can I rate-limit batch_edit_subscriptions? +

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

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

batch_edit_subscriptions is provided by the Inoreader MCP server (justmytwospence/inoreader-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.