create_records · Supabase MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_records does on Supabase MCP Server

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

This tool creates or inserts data into a database table, which is a Write operation. It modifies data in a reversible manner—records can be deleted afterward. Severity is medium because misuse could inject unwanted data into production systems, potentially causing data integrity issues, but the effect is not irreversible and can be remediated.

From the tool's definition Tool name 'create_records' and description explicitly states 'Create one or more records in a Supabase table'. The action is reversible via delete_records (a sibling tool), confirming it is Write rather than Destructive.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_records Rate-limited

create_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": {
    "create_records": {
      "limits": [
        {
          "counter": "create_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 create_records

What does the create_records tool do? +

Create one or more records in a Supabase table. 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 create_records? +

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

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

Can I rate-limit create_records? +

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

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

create_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.