supabase_insert_rows
Insert one or more rows into a Supabase table via PostgREST.
This record as markdown: /tools/shriram-vasudevan-integrations-mcp/supabase-insert-rows.md
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 supabase_insert_rows is rated Medium
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
The rule that runs supabase_insert_rows safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For supabase_insert_rows, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every supabase_insert_rows call is checked against it from then on.
Questions about supabase_insert_rows
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.
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.
supabase_insert_rows is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on Integrations, and thousands of servers like it.
This server
Across the catalogue