create_project
Creates a new Supabase project. Always ask the user which organization to create the project in. The project can take a few minutes to initialize - use get_project to check the status.
This record as markdown: /tools/supabase/create-project.md
What create_project does on Supabase
AI agents use create_project to create or update resources in Supabase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Supabase environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | The name of the project |
region | string | — | The region to create the project in. |
confirm_cost_id | string | — | The cost confirmation ID. Call `confirm_cost` first. |
organization_id | string | — |
Parameters from the server's own tool schema.
Why create_project is rated Medium
This tool creates new projects in Supabase organizations, which allocates cloud resources, establishes databases, and configures infrastructure. While reversible (projects can be deleted), this is fundamentally a resource creation action that modifies the organization's infrastructure state and typically incurs costs.
From the tool's definition Creates a new Supabase project with resource allocation and infrastructure provisioning. The tool description explicitly states it 'Creates a new Supabase project', which involves creating and initializing cloud infrastructure resources.
Attacks that exploit this kind of access
The rule that runs create_project safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Supabase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_project, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Supabase, apply this rule, and every create_project call is checked against it from then on.
Questions about create_project
Creates a new Supabase project. Always ask the user which organization to create the project in. The project can take a few minutes to initialize - use get_project to check the status. It is categorised as a Write tool in the Supabase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_project accepts 4 parameters: name, region, confirm_cost_id, organization_id. The full parameter table on this page comes from the server's own tool schema.
Register the Supabase MCP server in PolicyLayer and add a rule for 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 Supabase. Nothing to install.
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 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 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.
create_project is provided by the Supabase MCP server (@modelcontextprotocol/server-supabase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Supabase, and thousands of servers like it.
This server
Across the catalogue