Crawl and spider a documentation website to extract content
AI agents call spider_docs to retrieve information from Spider MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool crawls and extracts content from documentation websites, which is fundamentally a retrieval operation with no side effects on the target system. While web crawling can have resource implications (bandwidth, rate-limiting), it does not create, modify, delete, or execute code. The primary function is to collect and present existing data, fitting squarely within the Read category.
From the tool's definition Tool name 'spider_docs' and description 'Crawl and spider a documentation website to extract content' indicate data retrieval operations. No mention of modification, deletion, code execution, or financial operations.
Attacks that exploit this kind of access
Crawl and spider a documentation website to extract content. It is categorised as a Read tool in the Spider MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Spider MCP Server MCP server in PolicyLayer and add a rule for spider_docs: 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 Spider MCP Server. Nothing to install.
spider_docs 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 spider_docs 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 spider_docs. 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.
spider_docs is provided by the Spider MCP Server MCP server (oeo/spider-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →