Create a new Stitch project. Returns the project ID needed for sp_generate and sp_auto.
AI agents use sp_create_project 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 a new project resource, which is a reversible write operation. It does not execute arbitrary code, delete data, move money, or produce destructive effects. The project ID it returns is used by other tools (sp_generate, sp_auto) but the creation itself is a straightforward write action with low blast radius—projects can be deleted or modified later.
From the tool's definition Tool name 'sp_create_project' and description 'Create a new Stitch project' indicate data creation. Returns a project ID that enables downstream operations.
Documented attack patterns abuse exactly the kind of access sp_create_project 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_create_project:
{
"version": "1",
"default": "deny",
"tools": {
"sp_create_project": {
"limits": [
{
"counter": "sp_create_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sp_create_project 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.
Create a new Stitch project. Returns the project ID needed for sp_generate and sp_auto. 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_create_project: 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_create_project 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_create_project 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_create_project. 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_create_project 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.