Medium Risk

audit_accessibility

Audit a component for WCAG 2.1 accessibility violations. Checks color contrast hints, ARIA attributes, keyboard navigation, semantic HTML, form labels, focus management, and more. Returns issues with severity, suggestions, and WCAG criteria references.

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

@forgespace/ui-mcp Write Risk 2/5

AI agents use audit_accessibility to create or modify resources in Ui. 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_accessibility 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 Ui.

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

io-github-forge-space-ui-mcp.yaml
tools:
  audit_accessibility:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Ui policy for all 38 tools.

Tool Name audit_accessibility
Category Write
MCP Server Ui MCP Server
Risk Level Medium

View all 38 tools →

Agents calling write-class tools like audit_accessibility 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_accessibility tool do? +

Audit a component for WCAG 2.1 accessibility violations. Checks color contrast hints, ARIA attributes, keyboard navigation, semantic HTML, form labels, focus management, and more. Returns issues with severity, suggestions, and WCAG criteria references.. It is categorised as a Write tool in the Ui 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_accessibility? +

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

What risk level is audit_accessibility? +

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

Can I rate-limit audit_accessibility? +

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

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

audit_accessibility is provided by the Ui MCP server (@forgespace/ui-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Ui

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.