Medium Risk

audit_site

Full AI visibility audit across 58+ checks in 12 categories (4 AEO + 4 GEO + 4 Agent Readiness). Returns detailed per-check scores with specific issues and recommendations, AI Identity Card with mention readiness and detected competitors, and business profile. GEO checks include 3 research-backed...

Accepts URL/endpoint input (url)

Part of the AEO Scanner MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

aeo-scanner Write Risk 2/5

AI agents use audit_site to create or modify resources in AEO Scanner. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call audit_site repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach AEO Scanner.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

aeo-scanner.yaml
tools:
  audit_site:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full AEO Scanner policy for all 4 tools.

Tool Name audit_site
Category Write
Risk Level Medium

Agents calling write-class tools like audit_site have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the audit_site tool do? +

Full AI visibility audit across 58+ checks in 12 categories (4 AEO + 4 GEO + 4 Agent Readiness). Returns detailed per-check scores with specific issues and recommendations, AI Identity Card with mention readiness and detected competitors, and business profile. GEO checks include 3 research-backed citation signals: factual density, answer frontloading, and source citations. Does NOT generate fix code — use fix_site for that, or compare_sites to benchmark against a competitor. Requires API key ($1.00 per call). If you get payment_required, tell the user to set AEO_API_KEY.. It is categorised as a Write tool in the AEO Scanner MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on audit_site? +

Add a rule in your Intercept YAML policy under the tools section for audit_site. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AEO Scanner MCP server.

What risk level is audit_site? +

audit_site is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit audit_site? +

Yes. Add a rate_limit block to the audit_site rule in your Intercept 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.

How do I block audit_site completely? +

Set action: deny in the Intercept policy for audit_site. 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.

What MCP server provides audit_site? +

audit_site is provided by the AEO Scanner MCP server (aeo-scanner). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on AEO Scanner

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.