AI agents call crawl_website to retrieve information from ReActMCP Web Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the tool name 'crawl_website' and the context of a web search MCP server strongly suggest this retrieves/indexes web content. Web crawling is a Read operation—it fetches and analyzes web pages without modifying them. The confidence is not higher due to the missing description, but the category assignment is secure given the server's purpose and naming conventions of sibling tools.
From the tool's definition Tool name is 'crawl_website' with empty description. Sibling tools on this server include 'scrape_url' and 'search_web', which are Read operations.
Documented attack patterns abuse exactly the kind of access crawl_website gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ReActMCP Web Search, and nothing reaches the server without passing your rules. This is the rule we recommend for crawl_website:
{
"version": "1",
"default": "deny",
"tools": {
"crawl_website": {}
}
}crawl_website 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.
crawl_website. It is categorised as a Read tool in the ReActMCP Web Search MCP Server, which means it retrieves data without modifying state.
Register the ReActMCP Web Search MCP server in PolicyLayer and add a rule for crawl_website: 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 ReActMCP Web Search. Nothing to install.
crawl_website 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 crawl_website 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 crawl_website. 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.
crawl_website is provided by the ReActMCP Web Search MCP server (mshojaei77/reactmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ReActMCP Web Search, 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.
7 ReActMCP Web Search tools catalogued and risk-classified — across an index of 43,000+ MCP servers.