New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

push_migrations

A execute tool on the Supabase MCP Server - Self-Hosted Edition MCP server.

SERVERSupabase MCP Server - Self-Hosted Edition SOURCEabdqum/supabase-mcp-selfhosted
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about push_migrations

What does the push_migrations tool do? +

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.

How do I enforce a policy on push_migrations? +

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.

What risk level is push_migrations? +

push_migrations is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit push_migrations? +

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.

How do I block push_migrations completely? +

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.

What MCP server provides push_migrations? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Supabase MCP Server - Self-Hosted Edition's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.