Read rows from a Supabase table with optional filtering and column selection
AI agents call read_rows to retrieve information from Supabase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from a database table with filtering and column selection capabilities. It does not create, modify, or delete data. The presence of sibling tools (create_records, delete_records, update_records) confirms that destructive/write operations are separate.
From the tool's definition Tool name 'read_rows' and description 'Read rows from a Supabase table with optional filtering and column selection' explicitly indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Read rows from a Supabase table with optional filtering and column selection. It is categorised as a Read tool in the Supabase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Supabase MCP Server MCP server in PolicyLayer and add a rule for read_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 Supabase MCP Server. Nothing to install.
read_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 read_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 read_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.
read_rows 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.
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 →