// MCP TOOL REFERENCE

MCP ACCESSIBILITY BRIDGE TOOLS

8 tools from the MCP Accessibility Bridge MCP Server, categorised by risk level.

View the MCP Accessibility Bridge policy →

// ALL 8 MCP ACCESSIBILITY BRIDGE TOOLS

READ 5 tools

Read get_accessibility_tree Capture a snapshot of the current page\ Read get_element_properties Given a CSS selector, returns the element\ Read get_focused_element Returns the currently keyboard-focused element\ Read get_interactive_elements Find all interactive elements on the page (buttons, inputs, links, etc.) Read query_accessibility_tree Search the accessibility tree by ARIA role and/or accessible name.

EXECUTE 2 tools

Execute browser_navigate Navigate the connected browser to a URL. Execute browser_connect Connect to a running Chrome browser via the Chrome DevTools Protocol (CDP).

OTHER 1 tools

Other browser_disconnect Close the CDP connection to Chrome. Does NOT kill the Chrome process.

// FAQ

How many tools does the MCP Accessibility Bridge MCP server have? +

The MCP Accessibility Bridge MCP server exposes 8 tools across 3 categories: Read, Execute, Other.

How do I enforce policies on MCP Accessibility Bridge tools? +

Route the MCP Accessibility Bridge server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do MCP Accessibility Bridge tools fall into? +

MCP Accessibility Bridge tools are categorised as Read (5), Execute (2), Other (1). Each category has a recommended default policy.

Enforce policy on every MCP Accessibility Bridge tool call.

Start from MCP Accessibility Bridge, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.