get_ui_elements

THE RISK

Low Risk

Why get_ui_elements needs a policy

This tool only reads and returns structural information about UI elements (roles, names, positions) from an application window. It has no side effects, does not execute code, does not modify data, and does not trigger external operations. It is a passive information-gathering function consistent with the 'Read' category.

From the tool's definition Tool description states it 'Get[s] the accessibility tree of an app window' and 'Returns UI element roles, names, and positions' - purely retrieval operations with no modification or execution of code/commands.

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

POLICY

How to control get_ui_elements

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

policy.json

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

get_ui_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 Macos Control — 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 Macos Control tools

Execute execute_javascript Run JavaScript in the active browser tab. Much faster than screenshot+OCR for web pages. R Execute launch_app Open or focus a macOS application by name. Prefer batch_actions when combining with other Execute batch_actions PREFERRED: Always use this tool instead of calling individual action tools (click_at, type Execute click_at Click at x,y screen coordinates. Returns a screenshot by default (disable with return_scre Execute click_by_text Click a button, link, tab, radio, or checkbox by its visible text. Much more reliable than Execute click_element Click a named UI element in an app window. Returns a screenshot by default (disable with r Execute double_click_at Double-click at x,y screen coordinates. Returns a screenshot by default (disable with retu Execute open_url Open a URL in Safari or Chrome.

All 22 Macos Control 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_ui_elements

What does the get_ui_elements tool do? +

Get the accessibility tree of an app window. Returns UI element roles, names, and positions. It is categorised as a Read tool in the Macos Control MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_ui_elements? +

Register the Macos Control MCP server in PolicyLayer and add a rule for get_ui_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 Macos Control. Nothing to install.

What risk level is get_ui_elements? +

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

Can I rate-limit get_ui_elements? +

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

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

get_ui_elements is provided by the Macos Control MCP server (peterhdd/macos-control-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Macos Control tool call.

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

CHECK YOUR STACK →