supabase_insert_rows · Integrations MCP: Risk & Policy

WHAT IT DOES

What supabase_insert_rows does on Integrations MCP

AI agents use supabase_insert_rows to create or update resources in Integrations MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Integrations MCP environment.

WHY IT NEEDS A POLICY

Why supabase_insert_rows needs a policy

This tool creates new data records in a Supabase table, which is a reversible write operation. It does not execute arbitrary code (Execute), delete data (Destructive), or move money (Financial). The 'high' severity reflects that an AI agent with misguided instructions could insert large volumes of unwanted data, corrupt data integrity, or fill storage quota, though the operation remains reversible via deletion.

From the tool's definition Tool name 'supabase_insert_rows' and description 'Insert one or more rows into a Supabase table' explicitly indicates creating/adding new data rows to a database table.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

supabase_insert_rows Rate-limited

supabase_insert_rows 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": {
    "supabase_insert_rows": {
      "limits": [
        {
          "counter": "supabase_insert_rows_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 Integrations MCP, so you can run agents against it safely.

FAQ

Questions about supabase_insert_rows

What does the supabase_insert_rows tool do? +

Insert one or more rows into a Supabase table via PostgREST. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on supabase_insert_rows? +

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

What risk level is supabase_insert_rows? +

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

Can I rate-limit supabase_insert_rows? +

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

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

supabase_insert_rows is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.