// SCAN REPORT

Aria

21 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 29 Jun 2026

0 can modify or destroy data

21 read-only

21 tools total

Community server · catalogue entry verified 29/06/2026

How to control Aria ↓

TOOL MAP

What Aria exposes to your agents

Read (21) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Aria

PolicyLayer is an MCP gateway — it sits between your AI agents and Aria, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "check-name-requirements": {
    "limits": [
      {
        "counter": "check-name-requirements_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Aria — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ARIA →

Instant setup, no code required.

FULL CATALOGUE

All 21 Aria tools

READ 21 tools

Read check-name-requirements Check if a role requires an accessible name and how it can be provided. Read get-aria-version Get information about the ARIA specification version and metadata. Read get-attribute Get detailed information about an ARIA state or property (e.g., aria-label, aria-expanded, aria-hidden). Read get-global-attributes List all global ARIA states and properties that apply to any element. Read get-prohibited-attributes Get all prohibited ARIA attributes for a specific role. Read get-required-attributes Get all required ARIA attributes for a specific role. Read get-required-context Get the required parent context for a role (e.g., listitem requires list or group). Read get-required-owned Get the required child elements for a role (e.g., list requires listitem). Read get-role Get detailed information about a specific ARIA role including its description, properties, states, required co Read get-role-hierarchy Get the inheritance hierarchy for a role, showing parent and child roles. Read get-roles-requiring-name List all roles that require an accessible name. Read get-server-info Returns information about this MCP server. Read list-landmarks List all ARIA landmark roles with guidance on their proper usage. Read list-live-regions List all ARIA live region roles and explain their politeness levels. Read list-properties List all ARIA properties. Optionally filter to show only global properties. Read list-roles List all ARIA roles, optionally filtered by category. Categories: widget, composite, document, landmark, liveR Read list-states List all ARIA states with their descriptions. Read search-roles Search for ARIA roles by keyword in their name or description. Read suggest-role Suggest appropriate ARIA roles based on a description of the UI component. Read validate-role-attributes Validate which ARIA attributes are allowed, required, or prohibited for a specific role.

FAQ

Questions about Aria

Is the Aria MCP server safe to use without restrictions? +

The Aria server is primarily read-only with 21 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Aria MCP server expose? +

21 tools across 1 categories: Read. 21 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Aria? +

Register the Aria MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Aria tool call.

Deterministic rules across all 21 Aria tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ARIA →

Instant setup, no code required.

21 Aria tools catalogued and risk-classified — across an index of 43,000+ MCP servers.