AI agents use add_tag_to_item to create or update resources in RSS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RSS MCP Server environment.
This tool creates/modifies data (adding a tag to an article) without permanently destroying or overwriting content. It is a Write operation rather than Read (no query-only), Destructive (reversible), Execute (no code/command execution), Financial (no money involved), or Other.
From the tool's definition The tool 'add_tag_to_item' performs a data modification operation: it adds a tag to an article. The FreshRSS API context confirms this modifies persistent metadata associated with feed items. The action is reversible via tag removal.
Documented attack patterns abuse exactly the kind of access add_tag_to_item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RSS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_tag_to_item:
{
"version": "1",
"default": "deny",
"tools": {
"add_tag_to_item": {
"limits": [
{
"counter": "add_tag_to_item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} add_tag_to_item 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.
Free to start. No card required.
Adds a single tag to a specific article. It is categorised as a Write tool in the RSS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RSS MCP Server MCP server in PolicyLayer and add a rule for add_tag_to_item: 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 RSS MCP Server. Nothing to install.
add_tag_to_item 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 add_tag_to_item 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 add_tag_to_item. 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.
add_tag_to_item is provided by the RSS MCP Server MCP server (xueli-sherryli/rss-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from RSS MCP Server, 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.
34 RSS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.