RECOMMENDED FIRST STEP - Analyze sitemaps and create an intelligent sampling strategy for large sites. This tool is essential for job boards and large sites with 100k+ pages. Instead of crawling everything, it: 1. Discovers and validates all sitemaps (robots.txt + common locations) 2. Identifies ...
AI agents call plan_audit to retrieve information from SEO Audit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only analysis and planning operations: it discovers sitemaps, identifies patterns, estimates counts, and generates recommendations. It does not modify, execute, or delete any data. The output is informational (a sampling strategy and recommendations), making this a pure Read operation with low blast radius.
From the tool's definition Analyze sitemaps and create an intelligent sampling strategy... Discovers and validates all sitemaps... Identifies distinct route patterns... Estimates total pages per route type... Generates a smart sampling strategy
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
RECOMMENDED FIRST STEP - Analyze sitemaps and create an intelligent sampling strategy for large sites. This tool is essential for job boards and large sites with 100k+ pages. Instead of crawling everything, it: 1. Discovers and validates all sitemaps (robots.txt + common locations) 2. Identifies distinct route patterns (job pages, category pages, location pages, etc.) 3. Estimates total pages per route type 4. Generates a smart sampling strategy 5. Recommends which pages to analyze with Lighthouse Returns: - Sitemap validation (URL limits, lastmod coverage, compression) - Route pattern classification with estimated counts - Sampling strategy (how many pages to sample per type) - Issues, warnings, and recommendations Use this BEFORE crawl_site or sample_pages to understand site structure. It is categorised as a Read tool in the SEO Audit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SEO Audit MCP Server MCP server in PolicyLayer and add a rule for plan_audit: 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 SEO Audit MCP Server. Nothing to install.
plan_audit is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the plan_audit 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.
Set action: deny in the PolicyLayer policy for plan_audit. 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.
plan_audit is provided by the SEO Audit MCP Server MCP server (richarddillman/seo-audit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →