Apply different tags to different groups of articles in one call. Useful for triage workflows where you categorize items into multiple groups at once. Each operation is one API call. Costs 1 Zone 2 request per operation.
AI agents use batch_manage_tags 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.
Batch tag operations modify article attributes (tags/categories) but don't delete data or execute arbitrary code. This is a Write operation because tags are reversible metadata changes. Severity is medium because an AI agent could misapply tags across many articles at once, requiring manual correction, but the impact is recoverable and limited to metadata rather than data deletion or financial impact.
From the tool's definition Tool description states it 'Apply different tags to different groups of articles' and 'categorize items into multiple groups' — these are reversible modifications to article metadata. Tags can be added, removed, or changed without permanently destroying data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Apply different tags to different groups of articles in one call. Useful for triage workflows where you categorize items into multiple groups at once. Each operation is one API call. Costs 1 Zone 2 request per operation. 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.
Register the Inoreader MCP server in PolicyLayer and add a rule for batch_manage_tags: 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.
batch_manage_tags is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the batch_manage_tags 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.
Set action: deny in the PolicyLayer policy for batch_manage_tags. 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.
batch_manage_tags 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →