get_screen
Retrieves the details of a specific screen within a project.
This record as markdown: /tools/com-googleapis-stitch-mcp/get-screen.md
What get_screen does on Mcp
AI agents call get_screen to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Required. Identifier. The resource name of the screen to retrieve. Format: `projects/{project}/screens/{screen}` Example: `projects/4044680601076201931/screens/ |
screenId | string | Yes | Required. The screen ID of screen to retrieve. Example: `98b50e2ddc9943efb387052637738f61`, without the `screens/` prefix. |
projectId | string | Yes | Required. The project ID of screen to retrieve. Example: `4044680601076201931`, without the `projects/` prefix. |
Parameters from the server's own tool schema.
Why get_screen is rated Low
This tool performs a simple data retrieval operation ('Retrieves') without any side effects such as creation, modification, deletion, or execution of code. It falls squarely into the Read category as a query operation that returns information about an existing design system screen.
From the tool's definition Tool name 'get_screen' and description 'Retrieves the details of a specific screen within a project' indicate a data retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs get_screen safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_screen, this is the rule to start with:
get_screen is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every get_screen call is checked against it from then on.
Questions about get_screen
Retrieves the details of a specific screen within a project. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
get_screen accepts 3 parameters: name, screenId, projectId. Required: name, screenId, projectId. The full parameter table on this page comes from the server's own tool schema.
Register the 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 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 MCP server (https://stitch.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue