supabase_execute_sql · Integrations MCP: Risk & Policy

WHAT IT DOES

What supabase_execute_sql does on Integrations MCP

AI agents invoke supabase_execute_sql to trigger actions in Integrations MCP. 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 IT NEEDS A POLICY

Why supabase_execute_sql needs a policy

SQL execution is the Execute category by definition—it runs code whose effects depend entirely on the SQL argument provided. With an empty description, we cannot rule out destructive operations (DROP, DELETE, TRUNCATE) or data exfiltration. An AI agent given this tool without safeguards could easily drop tables, corrupt data, or extract sensitive information.

From the tool's definition Tool name 'supabase_execute_sql' explicitly indicates execution of SQL queries against a Supabase database. The 'execute_sql' verb combined with a database context means arbitrary SQL execution capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

supabase_execute_sql Rate-limited

supabase_execute_sql stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "supabase_execute_sql": {
      "limits": [
        {
          "counter": "supabase_execute_sql_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about supabase_execute_sql

What does the supabase_execute_sql tool do? +

supabase_execute_sql. It is categorised as a Execute tool in the Integrations MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on supabase_execute_sql? +

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

What risk level is supabase_execute_sql? +

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

Can I rate-limit supabase_execute_sql? +

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

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

supabase_execute_sql is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.