Low Risk

get_page_links

Extract all links from the current page.

How to control get_page_links ↓

What get_page_links does on MCP Web Browser Server

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

Low Risk

Why get_page_links needs a policy

This tool queries and retrieves link data from a webpage without causing side effects, creating data, executing code, or triggering external operations. It is a straightforward read operation that poses minimal risk even if misused by an AI agent, as it only extracts publicly visible page content.

From the tool's definition Tool name 'get_page_links' and description 'Extract all links from the current page' indicate passive data retrieval with no modification or execution of external actions.

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

How to control get_page_links

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

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

get_page_links 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 MCP Web Browser 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 get_page_links

What does the get_page_links tool do? +

Extract all links from the current page. It is categorised as a Read tool in the MCP Web Browser Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_page_links? +

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

What risk level is get_page_links? +

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

Can I rate-limit get_page_links? +

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

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

get_page_links is provided by the MCP Web Browser Server MCP server (random-robbie/mcp-web-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Web Browser Server tool call.

Start from MCP Web Browser 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.

6 MCP Web Browser 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.