Gets the storage config for a Supabase project.
AI agents call get_storage_config to retrieve information from Supabase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration data from a Supabase project's storage system. Reading configuration is a non-destructive, read-only operation. While storage config may contain sensitive settings, the act of retrieval itself poses minimal risk compared to tools that modify or delete data. Severity is low because exposure of this tool alone does not enable unauthorized modifications or financial transactions.
From the tool's definition Tool name 'get_storage_config' uses the 'get' verb, and description states 'Gets the storage config' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Gets the storage config for a Supabase project. It is categorised as a Read tool in the Supabase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Supabase MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_storage_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →