AI agents call ui_describe_all to retrieve information from Shotter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely queries and retrieves accessibility metadata about the current state of the iOS Simulator's UI. It performs no state changes, does not execute commands, does not delete anything, and does not involve financial operations. It is a read-only query function that returns descriptive information to support other actions.
From the tool's definition ui_describe_all: "Get accessibility information for all UI elements currently visible on screen. Returns element labels, types, and coordinates." The tool retrieves and returns data about UI elements with no modification or execution of actions.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get accessibility information for all UI elements currently visible on screen. Returns element labels, types, and coordinates. Useful for finding exact tap coordinates. It is categorised as a Read tool in the Shotter MCP Server, which means it retrieves data without modifying state.
Register the Shotter MCP server in PolicyLayer and add a rule for ui_describe_all: 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 Shotter. Nothing to install.
ui_describe_all 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_describe_all 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_describe_all. 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_describe_all is provided by the Shotter MCP server (nathanstitt/shotter). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →