beta_exchange_auth_code_for_users_access_and_refresh_token

WHAT IT DOES

What beta_exchange_auth_code_for_users_access_and_refresh_token does on Supabase Management API MCP Server

AI agents call beta_exchange_auth_code_for_users_access_and_refresh_token to retrieve information from Supabase Management API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

WHY IT NEEDS A POLICY

Why beta_exchange_auth_code_for_users_access_and_refresh_token needs a policy

Even though beta_exchange_auth_code_for_users_access_and_refresh_token only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

Questions about beta_exchange_auth_code_for_users_access_and_refresh_token

What does the beta_exchange_auth_code_for_users_access_and_refresh_token tool do? +

Exchange OAuth code for tokens. It is categorised as a Read tool in the Supabase Management API MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on beta_exchange_auth_code_for_users_access_and_refresh_token? +

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

What risk level is beta_exchange_auth_code_for_users_access_and_refresh_token? +

beta_exchange_auth_code_for_users_access_and_refresh_token is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit beta_exchange_auth_code_for_users_access_and_refresh_token? +

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

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

beta_exchange_auth_code_for_users_access_and_refresh_token is provided by the Supabase Management API MCP Server MCP server (zain4391/supabase_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.