AI agents call checkCrawlStatus to retrieve information from MCP-RSS-Crawler without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Checking crawl status is a read-only operation that retrieves information about an existing async task. It has no side effects, does not execute external code, does not modify data, and does not delete anything. The blast radius of misuse is minimal — an attacker could learn about ongoing crawl operations but cannot modify them or access sensitive content beyond what is already being crawled.
From the tool's definition Tool name is 'checkCrawlStatus' and description states 'Check the status of an asynchronous crawl' — this queries the status of a background operation without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access checkCrawlStatus 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 checkCrawlStatus:
{
"version": "1",
"default": "deny",
"tools": {
"checkCrawlStatus": {}
}
}checkCrawlStatus is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check the status of an asynchronous crawl. It is categorised as a Read tool in the MCP-RSS-Crawler MCP Server, which means it retrieves data without modifying state.
Register the MCP-RSS-Crawler MCP server in PolicyLayer and add a rule for checkCrawlStatus: 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.
checkCrawlStatus is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the checkCrawlStatus 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 checkCrawlStatus. 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.
checkCrawlStatus 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.