Get all interactive elements (buttons, inputs, selects, radios, checkboxes, links) from the current browser page. Returns structured text showing each element
AI agents call get_page_elements to retrieve information from Macos Control without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about page elements without executing commands, modifying data, or triggering side effects. It is a passive introspection capability used to understand what interactive components are available on a page. The context of other tools on the server (click_at, fill_by_label, execute_javascript) that perform actions reinforces that get_page_elements is a read-only helper.
From the tool's definition Tool description states it 'Get[s] all interactive elements' and 'Returns structured text showing each element' — purely retrieval of page structure with no modification or execution of actions.
Documented attack patterns abuse exactly the kind of access get_page_elements gives an agent:
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_page_elements:
{
"version": "1",
"default": "deny",
"tools": {
"get_page_elements": {}
}
}get_page_elements is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all interactive elements (buttons, inputs, selects, radios, checkboxes, links) from the current browser page. Returns structured text showing each element. It is categorised as a Read tool in the Macos Control MCP Server, which means it retrieves data without modifying state.
Register the Macos Control MCP server in PolicyLayer and add a rule for get_page_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.
get_page_elements 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 get_page_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.
Set action: deny in the PolicyLayer policy for get_page_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.
get_page_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.
Start from Macos Control, 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.
22 Macos Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.