Generate multiple related screens (e.g., login → dashboard → settings) in one call with consistent design
AI agents use sp_flow to create or update resources in Stitch Pro — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stitch Pro environment.
This tool creates/generates UI screens and design artifacts. It produces new content (screens) rather than reading existing data. It is not destructive or financial, and while it involves generation/execution of a design pipeline, the primary effect is creating new design output — fitting Write.
From the tool's definition Generate multiple related screens (e.g., login → dashboard → settings) in one call with consistent design
Documented attack patterns abuse exactly the kind of access sp_flow 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_flow:
{
"version": "1",
"default": "deny",
"tools": {
"sp_flow": {
"limits": [
{
"counter": "sp_flow_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sp_flow stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate multiple related screens (e.g., login → dashboard → settings) in one call with consistent design. It is categorised as a Write tool in the Stitch Pro MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Stitch Pro MCP server in PolicyLayer and add a rule for sp_flow: 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_flow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sp_flow 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_flow. 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_flow 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.