manage_extensions

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

SERVERSupabase MCP Server - Self-Hosted Edition SOURCEabdqum/supabase-mcp-selfhosted

Medium RISK CLASS

Category Write

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/manage-extensions.md

WHAT IT DOES

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

AI agents use manage_extensions to create or update resources in Supabase MCP Server - Self-Hosted Edition, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Supabase MCP Server - Self-Hosted Edition environment.

RISK

Why manage_extensions is rated Medium

Managing extensions in PostgreSQL can create, modify, or enable/disable extensions, which are reversible write operations. This is categorized as Write rather than Execute because extension management is primarily a configuration change, not arbitrary code execution. It ranks above Read due to its state-modifying nature, but below Destructive since extension operations are generally reversible.

From the tool's definition Tool name 'manage_extensions' on a Supabase MCP server with capabilities for 'database operations' and 'management' suggests the ability to enable, disable, or configure PostgreSQL extensions. The description is empty, limiting confidence.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs manage_extensions 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 manage_extensions, this is the rule to start with:

manage_extensions Rate-limited

manage_extensions stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage_extensions": {
      "limits": [
        {
          "counter": "manage_extensions_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Supabase MCP Server - Self-Hosted Edition, apply this rule, and every manage_extensions call is checked against it from then on.

FAQ

Questions about manage_extensions

What does the manage_extensions tool do? +

manage_extensions is a write tool on the Supabase MCP Server - Self-Hosted Edition MCP server. It is categorised as a Write tool in the Supabase MCP Server - Self-Hosted Edition MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage_extensions? +

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

manage_extensions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit manage_extensions? +

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

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

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

KEEP EXPLORING

More on Supabase MCP Server - Self-Hosted Edition, and thousands of servers like it.

This server

All 57 Supabase MCP Server - Self-Hosted Edition tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →