Updates the storage config for a Supabase project (requires a paid plan).
AI agents use update_storage_config to create or update resources in PostgREST — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PostgREST environment.
This tool modifies storage configuration settings for a Supabase project, which is a reversible write operation. While it affects project infrastructure, the changes are typically revertible through subsequent updates. It does not delete data (Destructive), execute arbitrary code (Execute), move money directly (Financial), or trigger external operations unpredictably (Execute).
From the tool's definition Tool name 'update_storage_config' and description 'Updates the storage config' indicate modification of configuration data. The mention of 'Supabase project' and 'requires a paid plan' suggests operational infrastructure changes.
Documented attack patterns abuse exactly the kind of access update_storage_config gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PostgREST, and nothing reaches the server without passing your rules. This is the rule we recommend for update_storage_config:
{
"version": "1",
"default": "deny",
"tools": {
"update_storage_config": {
"limits": [
{
"counter": "update_storage_config_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Updates the storage config for a Supabase project (requires a paid plan). It is categorised as a Write tool in the PostgREST MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PostgREST 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 PostgREST. Nothing to install.
update_storage_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
update_storage_config is provided by the PostgREST MCP server (supabase/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 32 PostgREST tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
32 PostgREST tools catalogued and risk-classified — across an index of 42,500+ MCP servers.