getArticlesByKeywords

THE RISK

Low Risk

Why getArticlesByKeywords needs a policy

This tool retrieves and filters articles based on keywords—a pure read operation with no side effects. It does not create, modify, delete, or execute external operations. The blast radius if misused is minimal: worst case, an AI agent retrieves irrelevant articles or queries repeatedly, but no data is modified or system resources are harmed.

From the tool's definition Tool name 'getArticlesByKeywords' and description 'Get articles matching user interest keywords' indicate a retrieval operation with no modification, deletion, or execution capability.

Documented attack patterns abuse exactly the kind of access getArticlesByKeywords gives an agent:

POLICY

How to control getArticlesByKeywords

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-RSS-Crawler, and nothing reaches the server without passing your rules. This is the rule we recommend for getArticlesByKeywords:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getArticlesByKeywords": {}
  }
}

getArticlesByKeywords is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register MCP-RSS-Crawler — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP-RSS-Crawler tools

Destructive removeKeyword Remove an interest keyword from the database Destructive removeRssFeed Remove an RSS feed from the database Execute cancelCrawl Cancel an asynchronous crawl job Execute asyncCrawlWebsite Start an asynchronous crawl of a website Write addKeyword Add a new interest keyword to the database Write addRssFeed Add a new RSS feed to the database Write crawlWebsite Crawl a website and save all pages to the database Read checkCrawlStatus Check the status of an asynchronous crawl

All 18 MCP-RSS-Crawler tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about getArticlesByKeywords

What does the getArticlesByKeywords tool do? +

Get articles matching user interest keywords. It is categorised as a Read tool in the MCP-RSS-Crawler MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getArticlesByKeywords? +

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

What risk level is getArticlesByKeywords? +

getArticlesByKeywords is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getArticlesByKeywords? +

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

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

getArticlesByKeywords is provided by the MCP-RSS-Crawler MCP server (mshk/mcp-rss-crawler). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP-RSS-Crawler tool call.

Start from MCP-RSS-Crawler, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →