set_tag · MCP RSS MCP: Risk & Policy

WHAT IT DOES

What set_tag does on MCP RSS

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

WHY IT NEEDS A POLICY

Why set_tag needs a policy

This tool modifies article state within the RSS feed management system (status transitions between unread, read, favorite, and archived). The changes are reversible—articles can be moved between states—so it qualifies as Write rather than Destructive. While archiving removes content from normal view, it does not permanently delete data.

From the tool's definition The tool description states it 'Update[s] article status' and 'Changes status of a single article by ID', enabling actions like 'mark as read', 'bookmark favorites', and 'archive' content. These are reversible modifications to article metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_tag Rate-limited

set_tag 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": {
    "set_tag": {
      "limits": [
        {
          "counter": "set_tag_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 MCP RSS, so you can run agents against it safely.

FAQ

Questions about set_tag

What does the set_tag tool do? +

Update article status for reading workflow management. Changes status of a single article by ID. Use to: mark as read after reading, bookmark favorites, archive irrelevant content. Status workflow: unread (default) → read (consumed) → favorite (bookmarked) → archived (hidden). Get article IDs from get_content/search_articles first. It is categorised as a Write tool in the MCP RSS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_tag? +

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

What risk level is set_tag? +

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

Can I rate-limit set_tag? +

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

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

set_tag is provided by the MCP RSS MCP server (ronnycoding/my_mcp_rss). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.