AI agents use addRssFeed to create or update resources in MCP-RSS-Crawler — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-RSS-Crawler environment.
This tool creates new records in a database, which is a Write operation. Severity is medium because while it modifies state, the impact is limited to adding configuration data—there is no direct access to sensitive user data, financial systems, or destructive operations. The confidence is high because the description clearly indicates database insertion/creation.
From the tool's definition The tool name is 'addRssFeed' and the description states it will 'Add a new RSS feed to the database', indicating data creation/modification in the backend storage.
Documented attack patterns abuse exactly the kind of access addRssFeed gives an agent:
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 addRssFeed:
{
"version": "1",
"default": "deny",
"tools": {
"addRssFeed": {
"limits": [
{
"counter": "addrssfeed_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} addRssFeed 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.
Add a new RSS feed to the database. It is categorised as a Write tool in the MCP-RSS-Crawler MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-RSS-Crawler MCP server in PolicyLayer and add a rule for addRssFeed: 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.
addRssFeed 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 addRssFeed 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 addRssFeed. 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.
addRssFeed 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.
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.
Free to start. No card required.
18 MCP-RSS-Crawler tools catalogued and risk-classified — across an index of 43,000+ MCP servers.