AI agents use rename_folder 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.
The tool creates or modifies data reversibly: it renames a folder and moves its contents, but does not delete or irreversibly destroy data. Users can rename folders back or move feeds elsewhere, making it a Write operation rather than Destructive. While it affects feed organization (potentially impacting many subscriptions), it remains reversible.
From the tool's definition "Rename a folder/label. All feeds in the old folder are moved to the new name." — directly modifies folder metadata and reorganizes feed collections.
Attacks that exploit this kind of access
Rename a folder/label. All feeds in the old folder are moved to the new name. 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.
Register the Inoreader MCP server in PolicyLayer and add a rule for rename_folder: 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.
rename_folder 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 rename_folder 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 rename_folder. 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.
rename_folder 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 →