list_organizations
Lists all organizations that the user is a member of.
This record as markdown: /tools/supabase/list-organizations.md
What list_organizations does on Supabase
AI agents call list_organizations to retrieve information from Supabase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_organizations is rated Low
This tool retrieves organizational membership information for the authenticated user. It performs a query operation without modifying, executing external operations, or deleting data. The blast radius is minimal—exposure could reveal organizational structure but poses no risk of unintended modifications or actions.
From the tool's definition Tool name 'list_organizations' combined with description 'Lists all organizations that the user is a member of' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_organizations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Supabase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_organizations, this is the rule to start with:
list_organizations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Supabase, apply this rule, and every list_organizations call is checked against it from then on.
Questions about list_organizations
Lists all organizations that the user is a member of. It is categorised as a Read tool in the Supabase MCP Server, which means it retrieves data without modifying state.
Register the Supabase 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. 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 (@modelcontextprotocol/server-supabase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Supabase, and thousands of servers like it.
This server
Across the catalogue