This record as markdown: /tools/supabase/pause-project.md
What pause_project does on Supabase
AI agents call pause_project to permanently remove resources in Supabase, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | — |
Parameters from the server's own tool schema.
Why pause_project is rated Critical
Pausing a project takes it offline, making it unavailable to users and applications. While not a permanent deletion, it is a disruptive, potentially hard-to-reverse action (especially if done unintentionally) that causes immediate service interruption. It goes beyond a simple write/update since it halts all project operations.
From the tool's definition pause_project' and 'Pauses a Supabase project'
Attacks that exploit this kind of access
The rule that runs pause_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 pause_project, this is the rule to start with:
pause_project is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Supabase, apply this rule, and every pause_project call is checked against it from then on.
Questions about pause_project
Pauses a Supabase project. It is categorised as a Destructive tool in the Supabase MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
pause_project accepts 1 parameter: project_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 pause_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.
pause_project is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pause_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 pause_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.
pause_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.
Across the catalogue