Low Risk

get_focused_element

Returns the currently keyboard-focused element\

How to control get_focused_element ↓

What get_focused_element does on MCP Accessibility Bridge

AI agents call get_focused_element to retrieve information from MCP Accessibility Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_focused_element needs a policy

This tool queries the current state of a browser's accessibility tree to identify which element has keyboard focus. It performs a read-only inspection with no capability to modify, delete, or execute actions. The blast radius of misuse is minimal—an AI agent could only retrieve information about what is currently focused, not alter browser state or trigger actions.

From the tool's definition Tool name 'get_focused_element' and description 'Returns the currently keyboard-focused element' indicate a retrieval operation with no side effects.

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

How to control get_focused_element

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_focused_element:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_focused_element": {}
  }
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_focused_element

What does the get_focused_element tool do? +

Returns the currently keyboard-focused element\. 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_focused_element? +

Register the MCP Accessibility Bridge MCP server in PolicyLayer and add a rule for get_focused_element: 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_focused_element? +

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

Can I rate-limit get_focused_element? +

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

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

get_focused_element 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.

Free to start. No card required.

8 MCP Accessibility Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.