This record as markdown: /tools/io-github-kivanccakmak-yaver/supabase-db.md
What supabase_db does on Yaver
AI agents invoke supabase_db to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | |
directory | string | — |
Parameters from the server's own tool schema.
Why supabase_db is rated High
While SQL execution *could* include destructive operations (DROP, DELETE, TRUNCATE), the description does not explicitly restrict the tool to read-only queries. An AI agent given this tool could execute any SQL statement, including data modification and deletion.
From the tool's definition Tool description states 'Execute SQL on Supabase database' — the verb 'Execute' combined with 'SQL' indicates the tool runs arbitrary database queries whose effects depend on the SQL arguments provided.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs supabase_db safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For supabase_db, this is the rule to start with:
supabase_db stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every supabase_db call is checked against it from then on.
Questions about supabase_db
Execute SQL on Supabase database. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
supabase_db accepts 2 parameters: query, directory. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for supabase_db: 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 Yaver. Nothing to install.
supabase_db is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the supabase_db 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 supabase_db. 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.
supabase_db is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue