// SCAN REPORT

Auth Fetch

4 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 11 Jun 2026

1 can modify or destroy data

3 read-only

4 tools total

Community server · catalogue entry verified 11/06/2026

How to control Auth Fetch ↓

TOOL MAP

Read (3) Write / Execute (1) Destructive / Financial (0)

MOST DANGEROUS TOOLS

High Risk

Execute · Medium close_browser This tool triggers an external browser operation (closing a browser window) and persists session state to disk.

1 of Auth Fetch's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

HOW TO CONTROL AUTH FETCH

PolicyLayer is an MCP gateway — it sits between your AI agents and Auth Fetch, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "auth_fetch": {
    "limits": [
      {
        "counter": "auth_fetch_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Auth Fetch — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON AUTH FETCH →

Free to start. No card required.

ALL 4 AUTH FETCH TOOLS

EXECUTE 1 tools

Execute close_browser Closes the browser window. Login sessions are saved and will be reused next time.

READ 3 tools

Read auth_fetch Fetches web page content using a real browser and returns cleaned HTML. Read download_media Downloads files from URLs using saved browser sessions. Read list_pages Lists all open tabs in the browser with their URLs and titles.

FAQ

Is the Auth Fetch MCP server safe to use without restrictions? +

The Auth Fetch server is primarily read-only with 3 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Auth Fetch MCP server expose? +

4 tools across 2 categories: Read, Write. 3 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Auth Fetch? +

Register the Auth Fetch MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Auth Fetch tool call.

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

ENFORCE POLICY ON AUTH FETCH →

Free to start. No card required.

4 Auth Fetch tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

Auth Fetch

// TOOL MAP

// MOST DANGEROUS TOOLS

// HOW TO CONTROL AUTH FETCH

// ALL 4 AUTH FETCH TOOLS

// FAQ

Enforce policy on every Auth Fetch tool call.

TOOL MAP

MOST DANGEROUS TOOLS

HOW TO CONTROL AUTH FETCH

ALL 4 AUTH FETCH TOOLS

FAQ