Generate complete Row Level Security (RLS) policies for Supabase — SELECT, INSERT, UPDATE, DELETE policies for each table and role combination. Includes security notes and server-only table restrictions. Args: - tables (array of strings): Table names to generate policies for - roles (array of str...
AI agents use briefkit_generate_rls_policies to create or update resources in Briefkit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Briefkit environment.
This is a Write tool because it generates SQL code that creates or modifies database security policies—a reversible but significant change to database access control. While the tool itself doesn't execute the SQL (hence not Execute), it produces production-ready SQL policies that, when applied, alter database security posture.
From the tool's definition Tool generates complete SQL RLS policies including CREATE POLICY and ENABLE RLS statements that modify database security configurations; explicitly returns SQL meant to be executed on Supabase databases; handles sensitive table restrictions (payments,…
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Generate complete Row Level Security (RLS) policies for Supabase — SELECT, INSERT, UPDATE, DELETE policies for each table and role combination. Includes security notes and server-only table restrictions. Args: - tables (array of strings): Table names to generate policies for - roles (array of strings): User roles in the application Returns: Complete SQL with RLS enable statements, per-table policies, admin overrides, and security notes. Handles server-only tables (payments, audit_log, webhook_events) automatically. Examples: -. It is categorised as a Write tool in the Briefkit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Briefkit MCP server in PolicyLayer and add a rule for briefkit_generate_rls_policies: 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 Briefkit. Nothing to install.
briefkit_generate_rls_policies 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 briefkit_generate_rls_policies 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 briefkit_generate_rls_policies. 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.
briefkit_generate_rls_policies is provided by the Briefkit MCP server (mithun4elp/briefkit-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 →