confirm_cost
Ask the user to confirm their understanding of the cost of creating a new project or branch. Call get_cost first. Returns a unique ID for this confirmation which should be passed to create_project or create_branch.
This record as markdown: /tools/supabase/confirm-cost.md
What confirm_cost does on Supabase
AI agents use confirm_cost to commit financial operations through Supabase, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | |
amount | number | — | |
recurrence | string | — |
Parameters from the server's own tool schema.
Why confirm_cost is rated Critical
This tool is a precursor step to financial commitment — it confirms user acknowledgment of costs associated with paid Supabase resources (projects/branches). While it doesn't directly move money, it gates financial transactions and its output (a confirmation ID) is required to proceed with cost-incurring operations, making it part of a financial workflow.
From the tool's definition 'confirm their understanding of the cost of creating a new project or branch' and 'Returns a unique ID for this confirmation which should be passed to `create_project` or `create_branch`'
Attacks that exploit this kind of access
The rule that runs confirm_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 confirm_cost, this is the rule to start with:
Any call to confirm_cost is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Supabase, apply this rule, and every confirm_cost call is checked against it from then on.
Questions about confirm_cost
Ask the user to confirm their understanding of the cost of creating a new project or branch. Call get_cost first. Returns a unique ID for this confirmation which should be passed to create_project or create_branch. It is categorised as a Financial tool in the Supabase MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
confirm_cost accepts 3 parameters: type, amount, recurrence. 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 confirm_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.
confirm_cost is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the confirm_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 confirm_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.
confirm_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.
Across the catalogue