@integrity-labs/cloud-broker 0.7.9 → 0.7.11

package/dist/index.js

@@ -21364,6 +21364,32 @@ var BrokerClient = class {
       { query: this.agentId ? { agent_id: this.agentId } : void 0 }
     );
   }
+  // ENG-7326 Phase 1: capability tools. Server-side scoped execution - the
+  // agent never receives a database credential.
+  supabaseQuery(args) {
+    return this.request(
+      "POST",
+      `/supabase/grants/${encodeURIComponent(args.grant_id)}/query`,
+      { query: this.agentId ? { agent_id: this.agentId } : void 0, body: { sql: args.sql } }
+    );
+  }
+  supabaseDescribe(args) {
+    return this.request(
+      "GET",
+      `/supabase/grants/${encodeURIComponent(args.grant_id)}/describe`,
+      { query: this.agentId ? { agent_id: this.agentId } : void 0 }
+    );
+  }
+  supabaseRest(args) {
+    return this.request(
+      "POST",
+      `/supabase/grants/${encodeURIComponent(args.grant_id)}/rest`,
+      {
+        query: this.agentId ? { agent_id: this.agentId } : void 0,
+        body: { method: args.method, path: args.path, ...args.body !== void 0 ? { body: args.body } : {} }
+      }
+    );
+  }
 };
 
 // src/inventory.ts
@@ -21590,6 +21616,19 @@ var supabaseCheckApprovalChannelSchema = external_exports.object({
   project_ref: supabaseProjectRefSchema
 });
 var supabaseListProjectsSchema = external_exports.object({});
+var supabaseQuerySchema = external_exports.object({
+  grant_id: external_exports.string().uuid("grant_id must be a UUID"),
+  sql: external_exports.string().min(1, "sql is required").describe("Read-only SQL to run server-side under your granted scope.")
+});
+var supabaseDescribeSchema = external_exports.object({
+  grant_id: external_exports.string().uuid("grant_id must be a UUID")
+});
+var supabaseRestSchema = external_exports.object({
+  grant_id: external_exports.string().uuid("grant_id must be a UUID"),
+  method: external_exports.enum(["GET", "HEAD", "POST", "PATCH", "PUT", "DELETE"]).describe("HTTP method. Writes require a non-read-only grant."),
+  path: external_exports.string().min(1, "path is required").describe('PostgREST-relative path, e.g. "orders?select=*&limit=10". Do NOT include /rest/v1/.'),
+  body: external_exports.unknown().optional().describe("JSON body for POST/PATCH/PUT.")
+});
 var supabaseDescribeScopeShape = supabaseDescribeScopeSchema.shape;
 var supabasePreviewRequestShape = supabasePreviewRequestSchema.shape;
 var supabaseRequestAccessShape = supabaseRequestAccessSchema.shape;
@@ -21598,11 +21637,14 @@ var supabaseReleaseAccessShape = supabaseReleaseAccessSchema.shape;
 var supabaseGetCredentialsShape = supabaseGetCredentialsSchema.shape;
 var supabaseCheckApprovalChannelShape = supabaseCheckApprovalChannelSchema.shape;
 var supabaseListProjectsShape = supabaseListProjectsSchema.shape;
+var supabaseQueryShape = supabaseQuerySchema.shape;
+var supabaseDescribeShape = supabaseDescribeSchema.shape;
+var supabaseRestShape = supabaseRestSchema.shape;
 
 // package.json
 var package_default = {
   name: "@integrity-labs/cloud-broker",
-  version: "0.7.9",
+  version: "0.7.11",
   description: "Cloud Access Broker \u2014 MCP server that mints scoped, TTL-bounded cloud credentials per agent task. Ships AWS support (aws_request_access, aws_poll_grant, aws_release_access, aws_describe_scope, aws_preview_request, aws_get_credentials \u2014 STS AssumeRole under the hood); GCP, Azure, and Cloudflare land alongside in the same package as the broker grows.",
   type: "module",
   bin: {
@@ -22080,6 +22122,45 @@ server.tool(
     }
   }
 );
+server.tool(
+  "supabase_describe",
+  "Inspect what an ACTIVE Supabase grant can actually do, BEFORE you run a query - so you never probe blindly. Takes a grant_id (from supabase_request_access). Returns { grant_id, status, project_ref, role, allowed_schemas, allowed_tables, read_only, expires_at, sql_query: { available, read_only_enforced, note } }. `sql_query.available` tells you whether server-side SQL is enabled for this project (an operator must have enrolled a scoped database credential); if false, supabase_query will 409 and you should tell the user the project is not set up for SQL access. Call this once after a grant goes active to learn your scope, then use supabase_query." + NO_DIRECT_SUPABASE_HTTP_BLOCK,
+  supabaseDescribeShape,
+  async (args) => {
+    try {
+      const result = await broker.supabaseDescribe(args);
+      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
+    } catch (err) {
+      return { content: [{ type: "text", text: formatBrokerError(err) }], isError: true };
+    }
+  }
+);
+server.tool(
+  "supabase_query",
+  "Run READ-ONLY SQL against a Supabase project for an ACTIVE grant. THIS is how you query Supabase - you do NOT get or hold a database credential, and the supabase_get_credentials JWT cannot run SQL. The broker executes your SQL server-side under the grant's scoped database role, inside a READ ONLY transaction with a statement timeout, and returns rows. Args: { grant_id, sql }. Returns on success { grant_id, ok: true, rows, row_count, truncated } (truncated=true means the row cap was hit - add LIMIT/aggregate). On failure returns { ok: false, error_code, error } where error_code is one of READ_ONLY (you attempted a write - this capability is read-only), SCOPE_DENIED (your grant's role can't access that object - try supabase_describe to see your scope), OBJECT_NOT_FOUND (no such relation/schema, or not visible to your grant), TIMEOUT (query too slow), SYNTAX_ERROR, UNREACHABLE, SQL_NOT_CONFIGURED (no scoped DB credential enrolled - tell the user to ask their operator to configure it), or a grant-state code GRANT_NOT_ACTIVE / GRANT_EXPIRED / GRANT_RELEASED (re-request access). Writes are always rejected. Call supabase_describe first if unsure what you can read. All of these come back in the { ok:false, error_code } envelope on a normal response - branch on error_code, do not treat them as tool failures." + NO_DIRECT_SUPABASE_HTTP_BLOCK,
+  supabaseQueryShape,
+  async (args) => {
+    try {
+      const result = await broker.supabaseQuery(args);
+      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
+    } catch (err) {
+      return { content: [{ type: "text", text: formatBrokerError(err) }], isError: true };
+    }
+  }
+);
+server.tool(
+  "supabase_rest",
+  'Call a Supabase project\'s REST (PostgREST) API for an ACTIVE grant - the primary way to read AND write your app data. You do NOT hold a key; the broker injects the project api_key and runs the call server-side under your grant\'s scope. Args: { grant_id, method (GET/HEAD/POST/PATCH/PUT/DELETE), path, body? }. `path` is PostgREST-relative - e.g. "orders?select=*&limit=10", "orders?id=eq.7" - do NOT include /rest/v1/ or the host. Filtering/ordering/pagination use PostgREST query syntax. For writes, pass the row(s) as `body` (POST=insert, PATCH=update with a filter in path, DELETE=delete with a filter in path). Returns on success { grant_id, ok: true, status, body } where body is the PostgREST JSON (rows for reads, the affected rows for writes). On a denial returns { ok: false, error_code, error }: READ_ONLY (your grant is read-only - writes rejected), SCOPE_DENIED (table not in your grant\'s allowed tables, or rpc/ blocked), BAD_REQUEST (bad method/path), REST_NOT_CONFIGURED (no api_key enrolled - tell the user to ask their operator), GRANT_NOT_ACTIVE / GRANT_EXPIRED / GRANT_RELEASED, or EXECUTION_ERROR. A 4xx from PostgREST itself comes back as { ok:false, status, body } with the upstream error in body. Call supabase_describe first to see your allowed tables and whether REST is available. rpc/ calls are not permitted. Use supabase_query for raw SQL / system tables instead.' + NO_DIRECT_SUPABASE_HTTP_BLOCK,
+  supabaseRestShape,
+  async (args) => {
+    try {
+      const result = await broker.supabaseRest(args);
+      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
+    } catch (err) {
+      return { content: [{ type: "text", text: formatBrokerError(err) }], isError: true };
+    }
+  }
+);
 var transport = new StdioServerTransport();
 await server.connect(transport);
 export {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@integrity-labs/cloud-broker",
-  "version": "0.7.9",
+  "version": "0.7.11",
   "description": "Cloud Access Broker — MCP server that mints scoped, TTL-bounded cloud credentials per agent task. Ships AWS support (aws_request_access, aws_poll_grant, aws_release_access, aws_describe_scope, aws_preview_request, aws_get_credentials — STS AssumeRole under the hood); GCP, Azure, and Cloudflare land alongside in the same package as the broker grows.",
   "type": "module",
   "bin": {