run_full_audit · aria51 MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_full_audit does on aria51 MCP Server

AI agents invoke run_full_audit to trigger actions in aria51 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.

WHY IT NEEDS A POLICY

Why run_full_audit needs a policy

This tool executes a series of automated audits and tests across a target website. While the operations themselves are read-only in their effects (no data is modified or deleted), the tool orchestrates multiple external scanning operations that are triggered by the AI agent's invocation. This falls under Execute category because it runs code/scanning operations whose effects depend on the URL argument provided.

From the tool's definition The tool 'run_full_audit' performs deterministic automated scanning and testing operations (page discovery, axe-core scanning, keyboard/structure/screen-reader audits) across a website.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_full_audit Rate-limited

run_full_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_full_audit": {
      "limits": [
        {
          "counter": "run_full_audit_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches aria51 MCP Server, so you can run agents against it safely.

FAQ

Questions about run_full_audit

What does the run_full_audit tool do? +

Run a complete WCAG compliance audit on a website. Discovers pages, scans with axe-core, runs keyboard/structure/screen-reader audits, and generates a prioritized remediation plan. No API key needed — all checks are deterministic. It is categorised as a Execute tool in the aria51 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_full_audit? +

Register the aria51 MCP Server MCP server in PolicyLayer and add a rule for run_full_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 aria51 MCP Server. Nothing to install.

What risk level is run_full_audit? +

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

Can I rate-limit run_full_audit? +

Yes. Add a rate_limit block to the run_full_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.

How do I block run_full_audit completely? +

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

What MCP server provides run_full_audit? +

run_full_audit is provided by the aria51 MCP Server MCP server (justinleeirizarry/aria51). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.