// MCP TOOL REFERENCE

WEB AUDITOR TOOLS

5 tools from the Web Auditor MCP Server, categorised by risk level.

READ TOOLS

get_history List recent inspection history. Optionally filter by URL substring. get_inspection Get detailed inspection results by inspection ID. Works for both single-page and site inspections. get_issues Get a filtered list of issues found during an inspection. Works with both single-page inspection_id and site_inspection_id. For site inspections, a... inspect_page Inspect a single web page for HTML/CSS quality, accessibility (WCAG/KWCAG), SEO, and performance/security. Returns scores, grades, and top issues. ... inspect_site Start a site-wide crawl and inspection. Crawls links from the root URL and inspects each page. Returns a site_inspection_id for tracking. Use get_i... 2/5

// FAQ

How many tools does the Web Auditor MCP server have? +

The Web Auditor MCP server exposes 5 tools across 1 categories: Read.

How do I enforce policies on Web Auditor tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Web Auditor server.

What risk categories do Web Auditor tools fall into? +

Web Auditor tools are categorised as Read (5). Each category has a recommended default policy.

Enforce policies on Web Auditor

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →