webcontext_map

Discover URLs belonging to a site Discover URLs belonging to a site without extracting page content. Results are deduplicated. HTTP: GET /v1/webcontext/map

SERVERReplyNodes SOURCEhttps://mcp.replynodes.com/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-replynodes-mcp/webcontext-map.md

WHAT IT DOES

What webcontext_map does on ReplyNodes

AI agents call webcontext_map 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.

Parameters from the server's own tool schema.

RISK

Why webcontext_map is rated Low

Tool enumerates URLs without fetching or modifying data; passive reconnaissance only.

From the tool's definition Discover URLs belonging to a site; no content extraction

Risk signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs webcontext_map 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_map, this is the rule to start with:

webcontext_map Allowed

webcontext_map is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "webcontext_map": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ReplyNodes, apply this rule, and every webcontext_map call is checked against it from then on.

FAQ

Questions about webcontext_map

What does the webcontext_map tool do? +

Discover URLs belonging to a site Discover URLs belonging to a site without extracting page content. Results are deduplicated. HTTP: GET /v1/webcontext/map. It is categorised as a Read tool in the ReplyNodes MCP Server, which means it retrieves data without modifying state.

What parameters does webcontext_map accept? +

webcontext_map accepts 1 parameter: url. Required: url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on webcontext_map? +

Register the ReplyNodes MCP server in PolicyLayer and add a rule for webcontext_map: 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.

What risk level is webcontext_map? +

webcontext_map is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit webcontext_map? +

Yes. Add a rate_limit block to the webcontext_map 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.

How do I block webcontext_map completely? +

Set action: deny in the PolicyLayer policy for webcontext_map. 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.

What MCP server provides webcontext_map? +

webcontext_map 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.

KEEP EXPLORING

More on ReplyNodes, and thousands of servers like it.

This server

All 66 ReplyNodes tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →