Describe what you want in plain English. Automatically chains design system creation, page generation, accessibility fixes, responsive adaptation, and framework conversion based on your intent.
AI agents invoke sp_auto to trigger actions in Stitch Pro. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool orchestrates multiple sub-operations automatically (create, generate, fix, adapt, convert) based on a natural language prompt. It triggers a pipeline of external operations whose scope and effects depend entirely on the user's input.
From the tool's definition Automatically chains design system creation, page generation, accessibility fixes, responsive adaptation, and framework conversion based on your intent
Documented attack patterns abuse exactly the kind of access sp_auto 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_auto:
{
"version": "1",
"default": "deny",
"tools": {
"sp_auto": {
"limits": [
{
"counter": "sp_auto_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}sp_auto stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Describe what you want in plain English. Automatically chains design system creation, page generation, accessibility fixes, responsive adaptation, and framework conversion based on your intent. It is categorised as a Execute tool in the Stitch Pro MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Stitch Pro MCP server in PolicyLayer and add a rule for sp_auto: 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_auto is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sp_auto 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_auto. 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_auto 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.