removeKeyword

THE RISK

Critical Risk

Why removeKeyword needs a policy

Removing a keyword from the database is an irreversible deletion operation. There is no indication of soft-delete or undo capability. While the blast radius is moderate (limited to keyword configuration data), the action cannot be undone, placing it in the Destructive category.

From the tool's definition 'Remove an interest keyword from the database' — permanently deletes a keyword record from the database

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

POLICY

How to control removeKeyword

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 removeKeyword:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "removeKeyword"
  ]
}

removeKeyword disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP-RSS-Crawler tools

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 Read fetchArticle Fetch an article from a specified URL using firecrawl

All 18 MCP-RSS-Crawler tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in MCP-RSS-Crawler → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about removeKeyword

What does the removeKeyword tool do? +

Remove an interest keyword from the database. It is categorised as a Destructive tool in the MCP-RSS-Crawler MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on removeKeyword? +

Register the MCP-RSS-Crawler MCP server in PolicyLayer and add a rule for removeKeyword: 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 removeKeyword? +

removeKeyword is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit removeKeyword? +

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

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

removeKeyword 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 →