refresh_feeds_tool · MCP Feed Reader MCP: Risk & Policy

WHAT IT DOES

What refresh_feeds_tool does on MCP Feed Reader

AI agents invoke refresh_feeds_tool to trigger actions in MCP Feed Reader. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why refresh_feeds_tool needs a policy

This tool initiates outbound network requests to crawl remote RSS/Atom feed URLs, which constitutes triggering external operations rather than a simple local read. While it doesn't modify user data destructively or involve finances, it does perform network I/O with side effects (updating the local SQLite cache, potentially hitting many remote servers).

From the tool's definition "Crawl feed sources over the network for new content" — triggers external network operations whose effects depend on the current state of remote sources

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

refresh_feeds_tool Rate-limited

refresh_feeds_tool stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "refresh_feeds_tool": {
      "limits": [
        {
          "counter": "refresh_feeds_tool_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 Feed Reader, so you can run agents against it safely.

FAQ

Questions about refresh_feeds_tool

What does the refresh_feeds_tool tool do? +

Crawl feed sources over the network for new content. Slow — takes 30-60s for all feeds. It is categorised as a Execute tool in the MCP Feed Reader MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on refresh_feeds_tool? +

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

What risk level is refresh_feeds_tool? +

refresh_feeds_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit refresh_feeds_tool? +

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

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

refresh_feeds_tool is provided by the MCP Feed Reader MCP server (pypi:mcp-feed-reader-crunchtools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.