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

auto_migrate

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/auto-migrate.md

What auto_migrate does on Supabase MCP Server - Self-Hosted Edition

AI agents invoke auto_migrate 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 auto_migrate is rated High

The tool name 'auto_migrate' strongly implies automated execution of database migrations, which can modify schema and data. The description is empty, lowering confidence. Given the context of a Supabase management server with migration-related sibling tools, this likely runs migrations automatically.

From the tool's definition Tool name 'auto_migrate' on a server with sibling tools like 'apply_migration' and 'create_migration' suggests automated database migration execution.

Questions about auto_migrate

What does the auto_migrate tool do? +

auto_migrate 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 auto_migrate? +

Register the Supabase MCP Server - Self-Hosted Edition MCP server in PolicyLayer and add a rule for auto_migrate: 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 auto_migrate? +

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

Can I rate-limit auto_migrate? +

Yes. Add a rate_limit block to the auto_migrate 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 auto_migrate completely? +

Set action: deny in the PolicyLayer policy for auto_migrate. 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 auto_migrate? +

auto_migrate 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.