Critical Risk →

reset_branch

Resets migrations of a development branch to a prior version.

How to control reset_branch ↓

AI agents call reset_branch to permanently remove resources in PostgREST — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

The tool performs a reset of migrations, which is inherently a destructive operation that cannot be undone. Resetting migrations on a branch will undo schema changes and potentially lose data or state.

From the tool's definition 'Resets migrations of a development branch to a prior version' — this operation irreversibly reverts database schema changes, potentially overwriting or discarding migration history and data transformations that cannot be automatically recovered.

Documented attack patterns abuse exactly the kind of access reset_branch gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and PostgREST, and nothing reaches the server without passing your rules. This is the rule we recommend for reset_branch:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "reset_branch"
  ]
}

reset_branch disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register PostgREST — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the reset_branch tool do? +

Resets migrations of a development branch to a prior version. It is categorised as a Destructive tool in the PostgREST MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on reset_branch? +

Register the PostgREST MCP server in PolicyLayer and add a rule for reset_branch: 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 PostgREST. Nothing to install.

What risk level is reset_branch? +

reset_branch is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit reset_branch? +

Yes. Add a rate_limit block to the reset_branch 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 reset_branch completely? +

Set action: deny in the PolicyLayer policy for reset_branch. 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 reset_branch? +

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

Enforce policy on every PostgREST tool call.

Deterministic rules across all 32 PostgREST tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

32 PostgREST tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.