Generate magic link, recovery link, or invite link
AI agents use supabase_generate_link to create or update resources in Supabase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Supabase MCP Server environment.
This tool creates authentication credentials and access links that are reversible (links can be revoked or expire). While it enables authentication workflows, generating these links constitutes data creation with side effects on the authentication system rather than destruction or financial impact. It is less severe than Execute (which would run arbitrary operations) but more than Read.
From the tool's definition Tool name 'supabase_generate_link' combined with description 'Generate magic link, recovery link, or invite link' indicates creation of authentication/access tokens.
Attacks that exploit this kind of access
Generate magic link, recovery link, or invite link. It is categorised as a Write tool in the Supabase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Supabase MCP Server MCP server in PolicyLayer and add a rule for supabase_generate_link: 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.
supabase_generate_link 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 supabase_generate_link 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 supabase_generate_link. 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.
supabase_generate_link is provided by the Supabase MCP Server MCP server (sweir1/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 →