supabase_select_rows

A read tool on the Integrations MCP server.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/supabase-select-rows.md

WHAT IT DOES

What supabase_select_rows does on Integrations MCP

AI agents call supabase_select_rows to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why supabase_select_rows is rated Low

The name 'select_rows' aligns with a SQL SELECT statement, which is a read operation that retrieves data without side effects. However, the empty description lowers confidence — it's possible the tool executes arbitrary SQL, which could include destructive operations. Based on naming convention alone, Read is the most likely category.

From the tool's definition Tool name contains 'select_rows', which strongly implies a SQL SELECT operation (data retrieval). Description is empty, providing no additional context.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs supabase_select_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_select_rows, this is the rule to start with:

supabase_select_rows Allowed

supabase_select_rows is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "supabase_select_rows": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every supabase_select_rows call is checked against it from then on.

FAQ

Questions about supabase_select_rows

What does the supabase_select_rows tool do? +

supabase_select_rows is a read tool on the Integrations MCP server. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on supabase_select_rows? +

Register the Integrations MCP server in PolicyLayer and add a rule for supabase_select_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_select_rows? +

supabase_select_rows is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit supabase_select_rows? +

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

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

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

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →