FULL AUDIT - Run a complete SEO audit with automatic sampling, caching, and report generation. This is the main audit tool that orchestrates the entire workflow: 1. Discovers and analyzes sitemaps 2. Identifies route patterns and creates sampling strategy 3. Captures sample pages (cached - only f...
AI agents invoke run_audit to trigger actions in SEO Audit MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a multi-step automated workflow that fetches external URLs, processes data, and writes files to disk. It spans Read and Write categories but is best classified as Execute because it triggers a complex orchestrated pipeline of external operations (crawling, fetching, analyzing) with side effects including file system writes (HTML snapshots, JSON files, reports).
From the tool's definition orchestrates the entire workflow... Discovers and analyzes sitemaps, Identifies route patterns, Captures sample pages, Analyzes SEO... Saves everything to reports/[sitename]/ folder
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
FULL AUDIT - Run a complete SEO audit with automatic sampling, caching, and report generation. This is the main audit tool that orchestrates the entire workflow: 1. Discovers and analyzes sitemaps 2. Identifies route patterns and creates sampling strategy 3. Captures sample pages (cached - only fetches once) 4. Analyzes SEO, structured data, technical issues, social graph 5. Generates prioritized recommendations 6. Saves everything to reports/[sitename]/ folder The audit captures pages ONCE and stores: - HTML snapshots for inspection - Full analysis data as JSON - Final report as JSON + Markdown Returns comprehensive findings and prioritized fix recommendations. It is categorised as a Execute tool in the SEO Audit MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SEO Audit MCP Server MCP server in PolicyLayer and add a rule for run_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.
run_audit is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_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 run_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.
run_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 →