Create a new Supabase project
AI agents use create_a_project to create or update resources in Supabase Management API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Supabase Management API MCP Server environment.
This tool creates a new Supabase project, which is a reversible Write operation. The severity is high because creating projects can incur financial costs, consume quotas, and create persistent infrastructure resources that require cleanup. However, it is categorized as Write rather than Financial because the tool itself does not directly transfer money—the financial impact is indirect through resource provisioning.
From the tool's definition Tool name is 'create_a_project' and description states 'Create a new Supabase project', indicating it creates a new resource.
Attacks that exploit this kind of access
Create a new Supabase project. It is categorised as a Write tool in the Supabase Management API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Supabase Management API MCP Server MCP server in PolicyLayer and add a rule for create_a_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 Management API MCP Server. Nothing to install.
create_a_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_a_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_a_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_a_project is provided by the Supabase Management API MCP Server MCP server (zain4391/supabase_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →