AI agents call list_organizations 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 queries and returns a list of organizations without creating, modifying, deleting, or executing any operations. It is a simple read operation that retrieves data. The blast radius is minimal as it only exposes metadata about existing organizations; misuse would result in unauthorized information disclosure rather than destructive or financial harm.
From the tool's definition Tool name is 'list_organizations' and description states 'List all organizations' — a retrieval operation with no modification or deletion.
Documented attack patterns abuse exactly the kind of access list_organizations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Supabase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_organizations:
{
"version": "1",
"default": "deny",
"tools": {
"list_organizations": {}
}
}list_organizations is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all organizations. 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 list_organizations: 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.
list_organizations 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 list_organizations 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 list_organizations. 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.
list_organizations is provided by the Supabase MCP Server MCP server (joshuarileydev/supabase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Supabase MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Supabase MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.