get_cost
Gets the cost of creating a new project or branch. Never assume organization as costs can be different for each.
This record as markdown: /tools/supabase/get-cost.md
What get_cost does on Supabase
AI agents call get_cost 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 |
|---|---|---|---|
type | string | — | |
organization_id | string | — | The organization ID. Always ask the user. |
Parameters from the server's own tool schema.
Why get_cost is rated Low
This tool queries pricing information and returns data without modifying, executing code, deleting resources, or committing financial transactions. It is informational only, designed to show costs before actions are taken. The sibling tool 'confirm_cost' would be the actual commitment; this is just a Read operation.
From the tool's definition Tool name is 'get_cost' and description states it 'Gets the cost of creating a new project or branch' - purely a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_cost 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_cost, this is the rule to start with:
get_cost 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_cost call is checked against it from then on.
Questions about get_cost
Gets the cost of creating a new project or branch. Never assume organization as costs can be different for each. It is categorised as a Read tool in the Supabase MCP Server, which means it retrieves data without modifying state.
get_cost accepts 2 parameters: type, organization_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_cost: 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_cost 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_cost 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_cost. 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_cost 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