Low Risk

fetch_page

Fetches web page text via Chromium PDF conversion and marker text extraction.

How to control fetch_page ↓

What fetch_page does on MCP Tools

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

Low Risk

Why fetch_page needs a policy

This tool retrieves and extracts text content from web pages using Chromium and PDF conversion. It performs a read-only operation with no side effects on the fetched resources or the system. The extracted text is returned for analysis but not modified on the source.

From the tool's definition Tool description states 'Fetches web page text' - the verb 'fetches' and the context of 'text extraction' indicate data retrieval without modification. No description of writing, executing code, deleting, or financial operations.

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

How to control fetch_page

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

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

fetch_page 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 Tools — 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 fetch_page

What does the fetch_page tool do? +

Fetches web page text via Chromium PDF conversion and marker text extraction. It is categorised as a Read tool in the MCP Tools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_page? +

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

What risk level is fetch_page? +

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

Can I rate-limit fetch_page? +

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

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

fetch_page is provided by the MCP Tools MCP server (zbigniewtomanek/my-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 MCP Tools tool call.

Start from MCP Tools, 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 Tools 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.