This record as markdown: /tools/io-github-kivanccakmak-yaver/supabase-migrations.md
What supabase_migrations does on Yaver
AI agents call supabase_migrations to retrieve information from Yaver 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 |
|---|---|---|---|
directory | string | — |
Parameters from the server's own tool schema.
Why supabase_migrations is rated Low
This tool performs a simple enumeration/query of Supabase migrations. It retrieves existing migration metadata for inspection purposes only, with no capability to create, modify, delete, or execute migrations. The 'list' verb and passive retrieval nature place it firmly in the Read category.
From the tool's definition Tool name and description indicate 'List Supabase migrations' — a read operation that retrieves and enumerates migration records without modifying data.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs supabase_migrations 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_migrations, this is the rule to start with:
supabase_migrations 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 Yaver, apply this rule, and every supabase_migrations call is checked against it from then on.
Questions about supabase_migrations
List Supabase migrations. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
supabase_migrations accepts 1 parameter: directory. 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_migrations: 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_migrations 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 supabase_migrations 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_migrations. 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_migrations 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.
This server
Across the catalogue