Low Risk

fetch_markdown

Fetch a website and return the content as Markdown

How to control fetch_markdown ↓

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

Low Risk

This tool retrieves and transforms existing web content into a different format (Markdown). No data is created, modified, deleted, or executed. The transformation is a presentation change only. The blast radius of misuse is limited to retrieving potentially sensitive content from publicly or privately accessible URLs, which is a read-level risk.

From the tool's definition Tool name is 'fetch_markdown' and description states 'Fetch a website and return the content as Markdown'. The verb 'fetch' and 'return' indicate retrieval without modification.

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

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

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

fetch_markdown 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 NPX Fetch — 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.

Go deeper

What does the fetch_markdown tool do? +

Fetch a website and return the content as Markdown. It is categorised as a Read tool in the MCP NPX Fetch MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_markdown? +

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

What risk level is fetch_markdown? +

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

Can I rate-limit fetch_markdown? +

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

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

fetch_markdown is provided by the MCP NPX Fetch MCP server (tokenizin-agency/mcp-npx-fetch). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP NPX Fetch tool call.

Deterministic rules across all 4 MCP NPX Fetch tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4 MCP NPX Fetch tools catalogued and risk-classified — across an index of 42,500+ 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.