Bulk-apply all SQL fixes from last audit, optionally filtered by severity. Wraps everything in a single transaction — if any statement fails, everything rolls back. Always preview the count and list before confirming.
AI agents use apply_all_fixes to create or update resources in Supabase Security — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Supabase Security environment.
An AI agent can call apply_all_fixes faster than any human can review — one bad instruction and it creates or modifies resources in Supabase Security by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Bulk-apply all SQL fixes from last audit, optionally filtered by severity. Wraps everything in a single transaction — if any statement fails, everything rolls back. Always preview the count and list before confirming. It is categorised as a Write tool in the Supabase Security MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Supabase Security MCP server in PolicyLayer and add a rule for apply_all_fixes: 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 Security. Nothing to install.
apply_all_fixes 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 apply_all_fixes 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 apply_all_fixes. 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.
apply_all_fixes is provided by the Supabase Security MCP server (perufitlife/supabase-security-mcp). 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 →