get_organization
Gets details for an organization. Includes subscription plan.
This record as markdown: /tools/supabase/get-organization.md
What get_organization does on Supabase
AI agents call get_organization 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | — | The organization ID |
Parameters from the server's own tool schema.
Why get_organization is rated Low
This tool retrieves organizational metadata including subscription plan information. While classified as Read (retrieval only, no modifications), the severity is medium rather than low because the subscription plan details could include sensitive billing/commercial information that, if exposed to an unauthorized AI agent, could reveal financial commitments, pricing tiers, or enable downstream financial decisions.
From the tool's definition Tool name is "get_organization" and description states it "Gets details for an organization. Includes subscription plan." This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_organization 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 get_organization, this is the rule to start with:
get_organization 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 get_organization call is checked against it from then on.
Questions about get_organization
Gets details for an organization. Includes subscription plan. It is categorised as a Read tool in the Supabase MCP Server, which means it retrieves data without modifying state.
get_organization accepts 1 parameter: id. The full parameter table on this page comes from the server's own tool schema.
Register the Supabase MCP server in PolicyLayer and add a rule for get_organization: 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.
get_organization 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 get_organization 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 get_organization. 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.
get_organization 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