get_screen
AI agents call get_screen to retrieve information from Stitch-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix universally denotes retrieval without modification. In the context of a design UI tool, fetching screen data produces no side effects and does not modify, execute, or delete data. This is a straightforward Read operation. Confidence is slightly reduced due to the empty description, but the tool naming and server context provide strong contextual evidence.
From the tool's definition Tool name 'get_screen' indicates a retrieval operation. The description is empty, but the naming convention and the pattern of sibling tools (get_project, list_projects, list_screens, list_design_systems) confirms this is a query/fetch tool.
Attacks that exploit this kind of access
get_screen. It is categorised as a Read tool in the Stitch-MCP MCP Server, which means it retrieves data without modifying state.
Register the Stitch- MCP server in PolicyLayer and add a rule for get_screen: 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 Stitch-MCP. Nothing to install.
get_screen 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 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. 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 is provided by the Stitch- MCP server (samueljayasingh/stitchmcp). 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 →