Gets the cost of a new project or branch for an organization.
AI agents call get_cost to retrieve information from Supabase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves cost information for estimation or planning purposes. It does not modify, delete, or execute any operations. While it relates to financial information (cost data), it only reads/queries that information rather than moving money, committing financial obligations, or making financial transactions. It is purely informational and falls under the Read category.
From the tool's definition Tool name is 'get_cost' and description states it 'Gets the cost of a new project or branch for an organization.' The verb 'Gets' indicates retrieval of information with no side effects.
Attacks that exploit this kind of access
Gets the cost of a new project or branch for an organization. It is categorised as a Read tool in the Supabase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Supabase MCP Server 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 MCP Server. 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 MCP server (pipethedev/supabase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →