High Risk →

audit_page

Audit HTML/CSS against Raven's design quality standards. Checks typography (min 13px, weight 400+, modular-scale heading ratios, line-height consistency), accessibility (WCAG touch targets, alt text, contrast), responsive patterns (flexbox over grid, clamp sizing, max-width containers), style gui...

Accepts raw HTML/template content (html)

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

raven-mcp Execute

AI agents invoke audit_page to trigger processes or run actions in Raven. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

audit_page can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

raven.yaml
tools:
  audit_page:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Raven policy for all 27 tools.

Tool Name audit_page
Category Execute
MCP Server Raven MCP Server
Risk Level High

View all 27 tools →

Agents calling execute-class tools like audit_page 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 Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

audit_page is one of the high-risk operations in Raven. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the audit_page tool do? +

Audit HTML/CSS against Raven's design quality standards. Checks typography (min 13px, weight 400+, modular-scale heading ratios, line-height consistency), accessibility (WCAG touch targets, alt text, contrast), responsive patterns (flexbox over grid, clamp sizing, max-width containers), style guide compliance (CSS custom properties, no bare hex), and visual rhythm (4/8px spacing grid, tight spacing scale, palette size). Returns pass/fail per check with specific fix instructions.. It is categorised as a Execute tool in the Raven MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on audit_page? +

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

What risk level is audit_page? +

audit_page is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit audit_page? +

Yes. Add a rate_limit block to the audit_page 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_page completely? +

Set action: deny in the Intercept policy for audit_page. 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_page? +

audit_page is provided by the Raven MCP server (raven-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.