AI agents use create_organization to create or update resources in Supabase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Supabase MCP Server environment.
This tool creates new data (a new organization) in a reversible manner. Organization creation can typically be undone by deletion. It does not execute arbitrary code, delete data irreversibly, move money, or merely read data. The medium severity reflects that an AI agent creating unwanted organizations could consume resources or create administrative overhead, but the impact is bounded and reversible.
From the tool's definition Tool name: 'create_organization'. Description: 'Create a new organization'. The tool creates a new entity (organization) in the Supabase management system.
Documented attack patterns abuse exactly the kind of access create_organization gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Supabase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_organization:
{
"version": "1",
"default": "deny",
"tools": {
"create_organization": {
"limits": [
{
"counter": "create_organization_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_organization 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 organization. It is categorised as a Write tool in the Supabase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Supabase MCP Server MCP server in PolicyLayer and add a rule for create_organization: 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 MCP Server. Nothing to install.
create_organization 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_organization 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_organization. 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_organization is provided by the Supabase MCP Server MCP server (joshuarileydev/supabase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Supabase MCP Server, 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.
8 Supabase MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.