AI agents call sp_screen to retrieve information from Stitch Pro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The sp_screen tool performs a read-only query operation that fetches and returns existing screen data (HTML and image). There are no side effects, no data modification, no code execution, and no destructive operations. This is a simple retrieval function with minimal risk if misused, as the worst case would be accessing unintended screen assets already stored in the system.
From the tool's definition Tool description states it retrieves a specific screen with 'HTML source and image URL' — pure data retrieval with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access sp_screen gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Stitch Pro, and nothing reaches the server without passing your rules. This is the rule we recommend for sp_screen:
{
"version": "1",
"default": "deny",
"tools": {
"sp_screen": {}
}
}sp_screen is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a specific screen with its HTML source and image URL. It is categorised as a Read tool in the Stitch Pro MCP Server, which means it retrieves data without modifying state.
Register the Stitch Pro MCP server in PolicyLayer and add a rule for sp_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 Pro. Nothing to install.
sp_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 sp_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 sp_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.
sp_screen is provided by the Stitch Pro MCP server (luciferdono/stitch-pro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Stitch Pro, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Stitch Pro tools catalogued and risk-classified — across an index of 43,000+ MCP servers.