Get the accessibility element tree of the current app. Useful for understanding the UI structure and finding elements to interact with.
AI agents call element_tree to retrieve information from ScreenHand without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that queries and returns UI structure information. It does not modify, delete, execute code, or trigger external operations. While the broader server enables Execute actions (via browser_click, applescript, etc.), this specific tool is purely informational.
From the tool's definition Tool retrieves the accessibility element tree of the current app to understand UI structure and find elements. The phrase "Get the accessibility element tree" and "for understanding" indicate this is a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access element_tree gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ScreenHand, and nothing reaches the server without passing your rules. This is the rule we recommend for element_tree:
{
"version": "1",
"default": "deny",
"tools": {
"element_tree": {}
}
}element_tree 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 the accessibility element tree of the current app. Useful for understanding the UI structure and finding elements to interact with. It is categorised as a Read tool in the ScreenHand MCP Server, which means it retrieves data without modifying state.
Register the ScreenHand MCP server in PolicyLayer and add a rule for element_tree: 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 ScreenHand. Nothing to install.
element_tree 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 element_tree 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 element_tree. 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.
element_tree is provided by the ScreenHand MCP server (manushi4/screenhand). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ScreenHand, 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.
89 ScreenHand tools catalogued and risk-classified — across an index of 43,000+ MCP servers.