restore_project
Restores a Supabase project.
This record as markdown: /tools/supabase/restore-project.md
What restore_project does on Supabase
AI agents use restore_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 |
|---|---|---|---|
project_id | string | — |
Parameters from the server's own tool schema.
Why restore_project is rated Medium
Restoring a project overwrites the current state with a previous snapshot, which is a significant write/overwrite operation. It could be considered destructive to the current state, but 'restore' typically implies recovery rather than deletion. However, it irreversibly replaces current data with restored data, pushing this toward high severity.
From the tool's definition 'Restores a Supabase project' — the word 'restore' implies bringing a project back to a prior state
Attacks that exploit this kind of access
The rule that runs restore_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 restore_project, this is the rule to start with:
restore_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 restore_project call is checked against it from then on.
Questions about restore_project
Restores a Supabase project. 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.
restore_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 restore_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.
restore_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 restore_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 restore_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.
restore_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