get_interactive_elements

THE RISK

Low Risk

Why get_interactive_elements needs a policy

This tool queries the accessibility tree to retrieve information about interactive elements. It performs no state modifications, no code execution, and no side effects—it is purely a read operation similar to 'get_element_properties' and 'query_accessibility_tree' on the same server.

From the tool's definition Tool is described as 'Find all interactive elements on the page' and is part of an accessibility inspection suite that 'read[s] element roles and states exactly as a screen reader would'.

Documented attack patterns abuse exactly the kind of access get_interactive_elements gives an agent:

POLICY

How to control get_interactive_elements

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Accessibility Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for get_interactive_elements:

policy.json

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

get_interactive_elements is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register MCP Accessibility Bridge — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Accessibility Bridge 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). 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 query_accessibility_tree Search the accessibility tree by ARIA role and/or accessible name. Other browser_disconnect Close the CDP connection to Chrome. Does NOT kill the Chrome process.

All 8 MCP Accessibility Bridge tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_interactive_elements

What does the get_interactive_elements tool do? +

Find all interactive elements on the page (buttons, inputs, links, etc.). It is categorised as a Read tool in the MCP Accessibility Bridge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_interactive_elements? +

Register the MCP Accessibility Bridge MCP server in PolicyLayer and add a rule for get_interactive_elements: 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 MCP Accessibility Bridge. Nothing to install.

What risk level is get_interactive_elements? +

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

Can I rate-limit get_interactive_elements? +

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

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

get_interactive_elements is provided by the MCP Accessibility Bridge MCP server (yashpreetbathla/mcp-accessibility-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

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 →