push_migrations
A execute tool on the Supabase MCP Server - Self-Hosted Edition MCP server.
This record as markdown: /tools/abdqum-supabase-mcp-selfhosted/push-migrations.md
What push_migrations does on Supabase MCP Server - Self-Hosted Edition
AI agents invoke push_migrations to trigger actions in Supabase MCP Server - Self-Hosted Edition. 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.
Why push_migrations is rated High
The name 'push_migrations' strongly implies applying database migrations to a Supabase instance, which executes schema changes (DDL operations like CREATE, ALTER, DROP). This is an Execute-level action at minimum, potentially Destructive if it involves dropping tables or columns. The description is empty, which lowers confidence.
From the tool's definition Tool name 'push_migrations' on a server with tools like 'apply_migration' and 'auto_migrate' suggests executing database schema changes
Attacks that exploit this kind of access
The rule that runs push_migrations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Supabase MCP Server - Self-Hosted Edition, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For push_migrations, this is the rule to start with:
push_migrations 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 Supabase MCP Server - Self-Hosted Edition, apply this rule, and every push_migrations call is checked against it from then on.
Questions about push_migrations
push_migrations is a execute tool on the Supabase MCP Server - Self-Hosted Edition MCP server. It is categorised as a Execute tool in the Supabase MCP Server - Self-Hosted Edition MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Supabase MCP Server - Self-Hosted Edition MCP server in PolicyLayer and add a rule for push_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 Supabase MCP Server - Self-Hosted Edition. Nothing to install.
push_migrations 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 push_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 push_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.
push_migrations is provided by the Supabase MCP Server - Self-Hosted Edition MCP server (abdqum/supabase-mcp-selfhosted). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Supabase MCP Server - Self-Hosted Edition, and thousands of servers like it.
This server
Across the catalogue