accessibility

Accessibility Guardian. audit: full WCAG audit of current screen. check: audit a single element. summary: quick score + counts. rules: list available 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.md

WHAT IT DOES

What accessibility does on Claude Mobile

AI agents call accessibility 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 is rated Low

The accessibility tool performs queries and inspections of screen accessibility properties (audit current screen, check single element, get quick score, list rules). These are non-destructive read operations that gather information about the UI state without triggering actions, executing code, or modifying device state.

From the tool's definition Tool provides audit, check, summary, and rules listing operations on accessibility—all are information retrieval with no modification or execution capabilities. No side effects mentioned.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs accessibility 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, this is the rule to start with:

accessibility Allowed

accessibility 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": {}
  }
}

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 call is checked against it from then on.

FAQ

Questions about accessibility

What does the accessibility tool do? +

Accessibility Guardian. audit: full WCAG audit of current screen. check: audit a single element. summary: quick score + counts. rules: list available 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? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for accessibility: 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? +

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

Can I rate-limit accessibility? +

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

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

accessibility 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 →