run_audit
Audit AND FIX a site for AI citation + SEO. Crawls the domain, scores AI-readability 0-10, checks for a v=AEO1 record, and returns the material needed to FIX it: seoReport.headSnippet is ready-to-paste <head> markup (title, meta description, Organization JSON-LD) and setup_prompt is a step-by-ste...
This record as markdown: /tools/com-groundedaeo-grounded-aeo/run-audit.md
What run_audit does on Grounded Aeo
AI agents invoke run_audit to trigger actions in Grounded Aeo. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain to audit, e.g. acme.com |
Parameters from the server's own tool schema.
Why run_audit is rated High
Tool crawls external sites and queues data changes, triggering external operations with side effects.
From the tool's definition Crawls the domain, scores AI-readability, queues extracted facts
Attacks that exploit this kind of access
The rule that runs run_audit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Grounded Aeo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_audit, this is the rule to start with:
run_audit stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Grounded Aeo, apply this rule, and every run_audit call is checked against it from then on.
Questions about run_audit
Audit AND FIX a site for AI citation + SEO. Crawls the domain, scores AI-readability 0-10, checks for a v=AEO1 record, and returns the material needed to FIX it: seoReport.headSnippet is ready-to-paste <head> markup (title, meta description, Organization JSON-LD) and setup_prompt is a step-by-step plan covering llms.txt, structured data, and AI-crawler access, plus a ranked list of gaps. Use it to build the fixes, apply them to the site, then CALL THIS AGAIN to verify the score improved and the gaps cleared. WRITE action (queues extracted facts, unverified until a human approves). Free, no account, rate-limited to 5/hour per caller. It is categorised as a Execute tool in the Grounded Aeo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
run_audit accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the Grounded Aeo 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 Grounded Aeo. 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 Grounded Aeo MCP server (https://groundedaeo.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Grounded Aeo, and thousands of servers like it.
Across the catalogue