Generate a complete Supabase/PostgreSQL database schema for a SaaS product — tables with column types, foreign keys, indexes, and a security baseline. Ready to run in Supabase SQL editor. Args: - product_name (string): Name of the SaaS product - saas_type (string): Type of SaaS — b2b, devtool, pr...
AI agents use briefkit_generate_database_schema 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.
The tool generates SQL schema code (CREATE TABLE, indexes, REVOKE statements) intended for execution in a production database environment. While the generated code itself is not executed by the tool, its primary purpose is to produce database-modifying SQL suitable for immediate application. This is a Write operation because schemas can be altered, dropped, or recreated.
From the tool's definition 'Generate a complete Supabase/PostgreSQL database schema' with 'CREATE TABLE statements' that are 'Ready to run in Supabase SQL editor' — this creates or modifies database structures reversibly via SQL DDL operations.
Attacks that exploit this kind of access
Generate a complete Supabase/PostgreSQL database schema for a SaaS product — tables with column types, foreign keys, indexes, and a security baseline. Ready to run in Supabase SQL editor. Args: - product_name (string): Name of the SaaS product - saas_type (string): Type of SaaS — b2b, devtool, productivity, marketplace, or microsaas - custom_tables (array of strings): Additional product-specific table names beyond the standard ones Returns: Complete SQL schema with CREATE TABLE statements, indexes, and security baseline (REVOKE statements for sensitive tables). 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_database_schema: 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_database_schema 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_database_schema 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_database_schema. 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_database_schema 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 →