update_storage_config · Supabase MCP Server MCP

WHAT IT DOES

What update_storage_config does on Supabase MCP Server

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

WHY IT NEEDS A POLICY

Why update_storage_config needs a policy

This tool creates or modifies configuration data reversibly (characteristic of Write category). While it affects project storage behavior, it does not delete data or execute arbitrary code. The high severity reflects that misconfigured storage settings could impact availability, permissions, or data access patterns for all users of the project, and the requirement for a paid plan suggests significant project scope.

From the tool's definition 'Updates the storage config for a Supabase project' — modifies project-level configuration settings that affect how file storage operates across the project.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_storage_config Rate-limited

update_storage_config 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": {
    "update_storage_config": {
      "limits": [
        {
          "counter": "update_storage_config_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Supabase MCP Server, so you can run agents against it safely.

FAQ

Questions about update_storage_config

What does the update_storage_config tool do? +

Updates the storage config for a Supabase project (requires a paid plan). It is categorised as a Write tool in the Supabase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_storage_config? +

Register the Supabase MCP Server MCP server in PolicyLayer and add a rule for update_storage_config: 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. Nothing to install.

What risk level is update_storage_config? +

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

Can I rate-limit update_storage_config? +

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

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

update_storage_config is provided by the Supabase MCP Server MCP server (pipethedev/supabase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.