Low Risk

accessibility_snapshot

Get the accessibility tree for any URL without needing a browser session. Returns a structured snapshot of all interactive elements, headings, links, buttons, form fields, images with alt text, and ARIA roles. Great for quick UX audits.

Accepts URL/endpoint input (url)

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

AI agents call accessibility_snapshot to retrieve information from Screenshotsmcp without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though accessibility_snapshot only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

relievedattention992-smithery-screenshotsmcp.yaml
tools:
  accessibility_snapshot:
    rules:
      - action: allow

See the full Screenshotsmcp policy for all 56 tools.

Tool Name accessibility_snapshot
Category Read
Risk Level Low

View all 56 tools →

Agents calling read-class tools like accessibility_snapshot 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 Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the accessibility_snapshot tool do? +

Get the accessibility tree for any URL without needing a browser session. Returns a structured snapshot of all interactive elements, headings, links, buttons, form fields, images with alt text, and ARIA roles. Great for quick UX audits.. It is categorised as a Read tool in the Screenshotsmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on accessibility_snapshot? +

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

What risk level is accessibility_snapshot? +

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

Can I rate-limit accessibility_snapshot? +

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

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

accessibility_snapshot is provided by the Screenshotsmcp MCP server (relievedattention992-smithery/screenshotsmcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Screenshotsmcp

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.