webcontext_crawl
Crawl same-origin links from a URL Crawl same-origin links starting from a URL and return normalized page results. max_pages/max_depth are clamped server-side regardless of the requested value. HTTP: GET /v1/webcontext/crawl
This record as markdown: /tools/com-replynodes-mcp/webcontext-crawl.md
What webcontext_crawl does on ReplyNodes
AI agents call webcontext_crawl to retrieve information from ReplyNodes without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Target URL to fetch. Rejected if it is malformed, uses a disallowed scheme, or resolves to a private/loopback/link-local/cloud-metadata address. |
max_depth | integer | — | Maximum link depth; clamped to 1..3. |
max_pages | integer | — | Maximum pages to crawl; clamped to 1..50. |
Parameters from the server's own tool schema.
Why webcontext_crawl is rated Low
Tool retrieves and aggregates publicly accessible web content with no modification, deletion, or execution capabilities.
From the tool's definition Crawl same-origin links from a URL and return normalized page results.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs webcontext_crawl safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ReplyNodes, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For webcontext_crawl, this is the rule to start with:
webcontext_crawl is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ReplyNodes, apply this rule, and every webcontext_crawl call is checked against it from then on.
Questions about webcontext_crawl
Crawl same-origin links from a URL Crawl same-origin links starting from a URL and return normalized page results. max_pages/max_depth are clamped server-side regardless of the requested value. HTTP: GET /v1/webcontext/crawl. It is categorised as a Read tool in the ReplyNodes MCP Server, which means it retrieves data without modifying state.
webcontext_crawl accepts 3 parameters: url, max_depth, max_pages. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the ReplyNodes MCP server in PolicyLayer and add a rule for webcontext_crawl: 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 ReplyNodes. Nothing to install.
webcontext_crawl 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 webcontext_crawl 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 webcontext_crawl. 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.
webcontext_crawl is provided by the ReplyNodes MCP server (https://mcp.replynodes.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ReplyNodes, and thousands of servers like it.
This server
Across the catalogue