Get screen context (UI tree and optional screenshot) with token-saving options.
AI agents call get_screen_summary to retrieve information from App Screen without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the current state of the screen and accessibility tree, returning information for observation. It has no side effects, does not execute commands, and does not modify or delete data. It is a foundational read operation in the observe-reason-act cycle described for the server.
From the tool's definition Tool description states 'Get screen context (UI tree and optional screenshot)' — retrieves UI information without modifying state. Name and description both indicate a read-only operation to obtain screen data.
Attacks that exploit this kind of access
Get screen context (UI tree and optional screenshot) with token-saving options. It is categorised as a Read tool in the App Screen MCP Server, which means it retrieves data without modifying state.
Register the App Screen MCP server in PolicyLayer and add a rule for get_screen_summary: 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 App Screen. Nothing to install.
get_screen_summary 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_screen_summary 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_screen_summary. 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_screen_summary is provided by the App Screen MCP server (xmuweili/app-screen-mcp). 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 →