// SCAN REPORT

Material Web

7 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 30 Jun 2026

0 can modify or destroy data

7 read-only

7 tools total

Community server · catalogue entry verified 30/06/2026

How to control Material Web ↓

TOOL MAP

What Material Web exposes to your agents

Read (7) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Material Web

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

Cap read operations

{
  "get_component_doc": {
    "limits": [
      {
        "counter": "get_component_doc_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 Material Web — 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 MATERIAL WEB →

Instant setup, no code required.

FULL CATALOGUE

All 7 Material Web tools

READ 7 tools

Read get_component_doc Returns the full documentation for a specific Material Web component Read get_installation_docs Returns the installation and quick-start documentation for Material Web Read get_theming_docs Returns the theming documentation for Material Web Read health_check Performs a health check on the server, verifying uptime, documentation accessibility, and basic functionality Read list_components Returns a JSON array of available Material Web component names Read search_docs Searches Material Web documentation for a keyword and returns matching file paths with excerpts Read validate_website Validates HTML code for correct Material Web component usage

FAQ

Questions about Material Web

Is the Material Web MCP server safe to use without restrictions? +

The Material Web server is primarily read-only with 7 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 Material Web MCP server expose? +

7 tools across 1 categories: Read. 7 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Material Web? +

Register the Material Web 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 Material Web tool call.

Deterministic rules across all 7 Material Web tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MATERIAL WEB →

Instant setup, no code required.

7 Material Web tools catalogued and risk-classified — across an index of 43,000+ MCP servers.