restore_project · Supabase MCP Server MCP: Risk & Policy

WHAT IT DOES

What restore_project does on Supabase MCP Server

AI agents use restore_project 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.

WHY IT NEEDS A POLICY

Why restore_project needs a policy

Restoring a project typically means reverting or recovering it from a backup or paused state, which is a write/modification operation. It could potentially overwrite current state, making it moderately to highly impactful. However, the description is very brief and uninformative, so confidence is moderate.

From the tool's definition 'Restores a project' — implies bringing a project back to a previous state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restore_project Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "restore_project": {
      "limits": [
        {
          "counter": "restore_project_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Supabase MCP Server, so you can run agents against it safely.

FAQ

Questions about restore_project

What does the restore_project tool do? +

Restores a project. 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.

How do I enforce a policy on restore_project? +

Register the Supabase MCP Server 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 MCP Server. Nothing to install.

What risk level is restore_project? +

restore_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit restore_project? +

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.

How do I block restore_project completely? +

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.

What MCP server provides restore_project? +

restore_project is provided by the Supabase MCP Server MCP server (pipethedev/supabase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.