# get_screen_code

Retrieve the HTML code download URL (and extract full HTML if possible) for a generated screen

Agent View of the PolicyLayer registry record for `get_screen_code`. HTML page: https://policylayer.com/tools/0x-professor-stitch-mcp-server/get-screen-code

## Facts

- Tool: `get_screen_code`
- Server: Stitch MCP Server (`0x-professor/stitch-mcp-server`) — https://policylayer.com/tools/0x-professor-stitch-mcp-server.md
- Homepage: https://github.com/0x-Professor/Stitch-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_screen_code",
    "arguments": {}
  }
}
```

## Why get_screen_code is rated Low

This tool retrieves and fetches existing HTML code without creating, modifying, deleting, or executing anything. It has no side effects beyond returning data. The operation is purely informational—fetching a download URL and viewing code does not alter any state. Low severity reflects minimal blast radius if misused; an agent could view unintended HTML code but cannot damage systems or data through this tool alone.

From the tool's own definition: "Tool is named 'get_screen_code' and described as 'Retrieve the HTML code download URL (and extract full HTML if possible)'. The verbs 'retrieve' and 'extract' indicate read-only operations with no data modification or deletion."

## Use case

AI agents call get_screen_code to retrieve information from Stitch MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Stitch MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_screen_code": {}
  }
}
```

## Other tools on Stitch MCP Server (8)

- `get_screen_image` — Read — https://policylayer.com/tools/0x-professor-stitch-mcp-server/get-screen-image.md
- `list_projects` — Read — https://policylayer.com/tools/0x-professor-stitch-mcp-server/list-projects.md
- `create_project` — Write — https://policylayer.com/tools/0x-professor-stitch-mcp-server/create-project.md
- `edit_screen` — Write — https://policylayer.com/tools/0x-professor-stitch-mcp-server/edit-screen.md
- `generate_and_fetch_code` — Write — https://policylayer.com/tools/0x-professor-stitch-mcp-server/generate-and-fetch-code.md
- `generate_screen` — Write — https://policylayer.com/tools/0x-professor-stitch-mcp-server/generate-screen.md
- `generate_variants` — Write — https://policylayer.com/tools/0x-professor-stitch-mcp-server/generate-variants.md
- `scaffold_project_files` — Write — https://policylayer.com/tools/0x-professor-stitch-mcp-server/scaffold-project-files.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0x-professor-stitch-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0x-professor-stitch-mcp-server