// SCAN REPORT

Dev Tool MCP

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

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

Last updated: 4 Jul 2026

1 can modify or destroy data

5 read-only

6 tools total

Community server · catalogue entry verified 04/07/2026

How to control Dev Tool MCP ↓

TOOL MAP

What Dev Tool MCP exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Dev Tool MCP tools

Write · Medium crawl_web_page The tool does more than read — it saves files to disk in multiple formats and downloads file resources, constituting a Write action.

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

POLICY

How to control Dev Tool MCP

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

Rate limit write operations

{
  "crawl_web_page": {
    "limits": [
      {
        "counter": "crawl_web_page_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "echo_message": {
    "limits": [
      {
        "counter": "echo_message_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 Dev Tool MCP — 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 DEV TOOL →

Instant setup, no code required.

FULL CATALOGUE

All 6 Dev Tool MCP tools

WRITE 1 tools

Write crawl_web_page Crawl web page content and save in multiple formats (HTML, JSON, PDF, screenshots) while downloading file reso

READ 5 tools

Read echo_message Echo tool that returns user-provided information as-is Read get_console_messages Capture console output information from specified URL webpage (including logs, warnings, errors, etc.) Read get_network_requests Monitor and retrieve all network requests initiated by specified URL webpage (API calls, resource loading, etc Read get_page_content Get complete content of a specified URL webpage, including HTML structure and page data Read say_hello A simple greeting tool that returns personalized messages to users

FAQ

Questions about Dev Tool MCP

How do I prevent bulk modifications through Dev Tool MCP? +

The Dev Tool MCP server has 1 write tools including crawl_web_page. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Dev Tool MCP.

How many tools does the Dev Tool MCP server expose? +

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

How do I enforce a policy on Dev Tool MCP? +

Register the Dev Tool 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 Dev Tool MCP tool call.

Deterministic rules across all 6 Dev Tool MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON DEV TOOL →

Instant setup, no code required.

6 Dev Tool MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.