Low Risk

extract_links_from_request

Extract and analyze all URLs/links from a captured request. Useful for finding password reset links, verification tokens, and other sensitive URLs.

How to control extract_links_from_request ↓

What extract_links_from_request does on Webhook Site MCP Server

AI agents call extract_links_from_request to retrieve information from Webhook Site MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why extract_links_from_request needs a policy

This tool retrieves and parses data from existing webhook requests without side effects. While it may reveal sensitive information like password reset links or tokens, the tool itself is read-only—it does not modify, delete, or execute any code or external operations.

From the tool's definition Tool performs extraction and analysis of URLs from already-captured requests ('Extract and analyze all URLs/links from a captured request'). No modification, deletion, or execution of requests or external systems occurs.

Documented attack patterns abuse exactly the kind of access extract_links_from_request gives an agent:

How to control extract_links_from_request

PolicyLayer is an MCP gateway — it sits between your AI agents and Webhook Site MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for extract_links_from_request:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "extract_links_from_request": {}
  }
}

extract_links_from_request is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Webhook Site MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about extract_links_from_request

What does the extract_links_from_request tool do? +

Extract and analyze all URLs/links from a captured request. Useful for finding password reset links, verification tokens, and other sensitive URLs. It is categorised as a Read tool in the Webhook Site MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on extract_links_from_request? +

Register the Webhook Site MCP Server MCP server in PolicyLayer and add a rule for extract_links_from_request: 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 Webhook Site MCP Server. Nothing to install.

What risk level is extract_links_from_request? +

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

Can I rate-limit extract_links_from_request? +

Yes. Add a rate_limit block to the extract_links_from_request 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 extract_links_from_request completely? +

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

extract_links_from_request is provided by the Webhook Site MCP Server MCP server (zebbern/webhook-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Webhook Site MCP Server tool call.

Start from Webhook Site MCP Server, 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.

23 Webhook Site MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.