List SQL snippets for a project
AI agents call lists_sql_snippets_for_the_logged_in_user to retrieve information from Supabase Management API 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 and queries SQL snippets stored for a user without executing them, modifying them, or causing side effects. It is a straightforward read operation that returns existing data. The severity is low because listing snippets poses minimal risk even if misused by an AI agent — the worst outcome is unauthorized viewing of user's SQL code.
From the tool's definition Tool name contains 'lists_sql_snippets' and description states 'List SQL snippets for a project' — pure retrieval operation with no modification or execution.
Attacks that exploit this kind of access
List SQL snippets for a project. It is categorised as a Read tool in the Supabase Management API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Supabase Management API MCP Server MCP server in PolicyLayer and add a rule for lists_sql_snippets_for_the_logged_in_user: 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 Management API MCP Server. Nothing to install.
lists_sql_snippets_for_the_logged_in_user 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 lists_sql_snippets_for_the_logged_in_user 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 lists_sql_snippets_for_the_logged_in_user. 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.
lists_sql_snippets_for_the_logged_in_user is provided by the Supabase Management API MCP Server MCP server (zain4391/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 →