accessibility_audit

Run full accessibility audit on current screen. Returns score, issues grouped by severity, and passed rules.

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexgladkov-claude-in-mobile/accessibility-audit.md

WHAT IT DOES

What accessibility_audit does on Claude Mobile

AI agents call accessibility_audit to retrieve information from Claude Mobile without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why accessibility_audit is rated Low

This tool reads and analyzes the current screen state to produce an accessibility report. It retrieves data (score, issues, passed rules) without modifying device state, executing commands, or causing any side effects.

From the tool's definition Run full accessibility audit on current screen. Returns score, issues grouped by severity, and passed rules.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs accessibility_audit safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For accessibility_audit, this is the rule to start with:

accessibility_audit Allowed

accessibility_audit is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "accessibility_audit": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every accessibility_audit call is checked against it from then on.

FAQ

Questions about accessibility_audit

What does the accessibility_audit tool do? +

Run full accessibility audit on current screen. Returns score, issues grouped by severity, and passed rules. It is categorised as a Read tool in the Claude Mobile MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on accessibility_audit? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for accessibility_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 Claude Mobile. Nothing to install.

What risk level is accessibility_audit? +

accessibility_audit is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit accessibility_audit? +

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

Set action: deny in the PolicyLayer policy for accessibility_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 accessibility_audit? +

accessibility_audit is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Mobile, and thousands of servers like it.

This server

All 198 Claude Mobile tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →