update_records · Supabase MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_records does on Supabase MCP Server

AI agents use update_records 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 update_records needs a policy

This tool creates or modifies data reversibly. While it mutates records in a database, the operation is reversible (data can be updated again or rolled back), distinguishing it from Destructive operations that cannot be undone. Severity is medium because misuse could corrupt important data, but the blast radius is limited by filter conditions and the ability to restore previous values.

From the tool's definition Tool name: 'update_records'; description: 'Update records in a Supabase table based on filter conditions' — explicitly updates (modifies) existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_records Rate-limited

update_records 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": {
    "update_records": {
      "limits": [
        {
          "counter": "update_records_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 update_records

What does the update_records tool do? +

Update records in a Supabase table based on filter conditions. 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 update_records? +

Register the Supabase MCP Server MCP server in PolicyLayer and add a rule for update_records: 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 update_records? +

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

Can I rate-limit update_records? +

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

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

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