supabase_select_rows
AI agents call supabase_select_rows to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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
supabase_select_rows. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
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.
supabase_select_rows is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →