ui_get_element
Re-resolves a previously returned element_ref (its bounds/state may have changed). Returns role, label, bounds, enabled, focused, value. stale_element if the handle is unknown or the element no longer exists.
This record as markdown: /tools/com-local-mcp-local-mcp/ui-get-element.md
What ui_get_element does on Local
AI agents call ui_get_element to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
element_ref | string | Yes |
Parameters from the server's own tool schema.
Why ui_get_element is rated Low
This is a pure read operation that queries UI element state without side effects. It supports other tools (like chrome_click or chrome_fill_form) by providing reference data, but performs no actions itself. The low severity reflects minimal risk even if misused—an attacker gains only visibility into UI structure and state, not control or data access.
From the tool's definition The tool 'ui_get_element' retrieves element properties (role, label, bounds, enabled, focused, value) with no modification capability. Description explicitly states it 're-resolves' and 'returns' data, with error handling for stale elements.
Attacks that exploit this kind of access
The rule that runs ui_get_element safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ui_get_element, this is the rule to start with:
ui_get_element is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every ui_get_element call is checked against it from then on.
Questions about ui_get_element
Re-resolves a previously returned element_ref (its bounds/state may have changed). Returns role, label, bounds, enabled, focused, value. stale_element if the handle is unknown or the element no longer exists. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
ui_get_element accepts 1 parameter: element_ref. Required: element_ref. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for ui_get_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 Local. Nothing to install.
ui_get_element is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ui_get_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.
Set action: deny in the PolicyLayer policy for ui_get_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.
ui_get_element is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue