Confirms the user's understanding of new project or branch costs. This is required to create a new project or branch.
AI agents use confirm_cost to commit financial operations through PostgREST — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool confirms financial commitment to incurring costs for new projects or branches. While it doesn't directly move money, it is a prerequisite gate that authorizes spending/billing obligations, making it Financial in nature. Misuse could lead an AI agent to automatically confirm cost commitments without explicit user awareness, resulting in unexpected cloud infrastructure charges.
From the tool's definition 'Confirms the user's understanding of new project or branch costs. This is required to create a new project or branch.'
Documented attack patterns abuse exactly the kind of access confirm_cost gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PostgREST, and nothing reaches the server without passing your rules. This is the rule we recommend for confirm_cost:
{
"version": "1",
"default": "deny",
"tools": {
"confirm_cost": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to confirm_cost is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Confirms the user's understanding of new project or branch costs. This is required to create a new project or branch. It is categorised as a Financial tool in the PostgREST MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the PostgREST 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 PostgREST. 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 PostgREST MCP server (supabase/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 32 PostgREST tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
32 PostgREST tools catalogued and risk-classified — across an index of 42,500+ MCP servers.