Crawl multi-page documentation.
AI agents call tool_crawl_docs to retrieve information from DevLens MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Crawling documentation is a read-only operation that retrieves and indexes web content. It has no side effects, does not execute code, does not modify or delete data, and does not involve financial transactions. The tool fits the 'Read' category as it searches and fetches information.
From the tool's definition Tool name 'tool_crawl_docs' and description 'Crawl multi-page documentation' indicate retrieval and aggregation of existing documentation content with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Crawl multi-page documentation. It is categorised as a Read tool in the DevLens MCP MCP Server, which means it retrieves data without modifying state.
Register the DevLens MCP server in PolicyLayer and add a rule for tool_crawl_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 DevLens MCP. Nothing to install.
tool_crawl_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 tool_crawl_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 tool_crawl_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.
tool_crawl_docs is provided by the DevLens MCP server (y4nn777/devlens-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 →