supabase_update_user · Integrations MCP: Risk & Policy

WHAT IT DOES

What supabase_update_user does on Integrations MCP

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

WHY IT NEEDS A POLICY

Why supabase_update_user needs a policy

This tool modifies user records in Supabase, affecting authentication, profiles, or related user data. While reversible (Write rather than Destructive), it poses high severity due to potential impact on user accounts, access control, and data integrity.

From the tool's definition Tool name 'supabase_update_user' indicates modification of user data. Supabase is a backend-as-a-service platform managing databases and authentication. The 'update' verb explicitly signals reversible data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

supabase_update_user Rate-limited

supabase_update_user 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": {
    "supabase_update_user": {
      "limits": [
        {
          "counter": "supabase_update_user_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 Integrations MCP, so you can run agents against it safely.

FAQ

Questions about supabase_update_user

What does the supabase_update_user tool do? +

supabase_update_user. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on supabase_update_user? +

Register the Integrations MCP server in PolicyLayer and add a rule for supabase_update_user: 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_update_user? +

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

Can I rate-limit supabase_update_user? +

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

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

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