@integrity-labs/cloud-broker 0.4.5 → 0.4.6

package/dist/index.js

@@ -20996,7 +20996,6 @@ var BrokerClient = class {
   host;
   agentId;
   runId;
-  defaultSourceContext;
   apiKey;
   fetchImpl;
   token;
@@ -21006,7 +21005,6 @@ var BrokerClient = class {
     this.host = config2.host.replace(/\/+$/, "");
     this.agentId = config2.agentId;
     this.runId = config2.runId;
-    this.defaultSourceContext = config2.defaultSourceContext;
     this.apiKey = config2.apiKey;
     this.fetchImpl = config2.fetchImpl ?? fetch;
     this.token = config2.initialToken ?? "";
@@ -21122,13 +21120,7 @@ var BrokerClient = class {
     if (!runId) {
       throw makeBrokerError(400, "BrokerClient.requestAccess requires run_id (pass it in args, or set runId on BrokerClientConfig)");
     }
-    const sourceContext = args.source_context ?? this.defaultSourceContext;
-    const body = {
-      ...args,
-      agent_id: agentId,
-      run_id: runId,
-      source_context: sourceContext
-    };
+    const body = { ...args, agent_id: agentId, run_id: runId };
     return this.request("POST", "/aws/grants", { body });
   }
   pollGrant(args) {
@@ -21222,14 +21214,6 @@ if (process.env.AGT_TEAM_SLUG) {
     "cloud-broker: AGT_TEAM_SLUG is set but no longer required (the API derives team from agent_id). Safe to remove from .mcp.json env block."
   );
 }
-var AGT_INBOUND_CHANNEL_TYPE = process.env.AGT_INBOUND_CHANNEL_TYPE ?? "";
-var AGT_INBOUND_CHANNEL_ID = process.env.AGT_INBOUND_CHANNEL_ID ?? "";
-var AGT_INBOUND_CHANNEL_THREAD_TS = process.env.AGT_INBOUND_CHANNEL_THREAD_TS ?? "";
-var defaultSourceContext = AGT_INBOUND_CHANNEL_TYPE && AGT_INBOUND_CHANNEL_ID ? {
-  channel_type: AGT_INBOUND_CHANNEL_TYPE,
-  channel_id: AGT_INBOUND_CHANNEL_ID,
-  thread_ts: AGT_INBOUND_CHANNEL_THREAD_TS || void 0
-} : void 0;
 var broker = new BrokerClient({
   host: AGT_HOST,
   agentId: AGT_AGENT_ID,
@@ -21237,7 +21221,6 @@ var broker = new BrokerClient({
   // Empty string is treated as absent — the broker client only fills runId
   // on requestAccess if a non-empty value is provided.
   runId: AGT_RUN_ID || void 0,
-  defaultSourceContext,
   initialToken: AGT_TOKEN || void 0,
   apiKey: AGT_API_KEY || void 0
 });
@@ -21280,7 +21263,7 @@ server.tool(
 );
 server.tool(
   "request_access",
-  `Request scoped, TTL-bounded AWS credentials for the current task. agent_id and run_id are optional \u2014 the broker fills them from the host MCP env (AGT_AGENT_ID / AGT_RUN_ID). source_context is also optional \u2014 the broker fills channel_type/channel_id/thread_ts from AGT_INBOUND_CHANNEL_* env when the host runtime exposes them, so the resolution notification can tell you to thread the answer back to the original conversation. Pass source_context explicitly only when you know it differs from the inbound message you are currently handling (rare). Returns { grant_id, status, secret_ref?, expires_at?, denial_reason?, notification_status?, notification_failure_reason? }. status="active" means credentials are ready, use them now. status="denied" means the request was rejected (denial_reason explains). status="pending" means approval is still outstanding \u2014 DO NOT poll. The broker pushes the resolution to you via direct-chat the moment a human approves or denies, so save the grant_id, return control, and resume when the inbound message arrives. The notification body will include the source channel/thread to reply in \u2014 complete the user's task there, not in direct-chat. Only check notification_status if you need to flag a setup issue to the user: "sent" means a human was paged; "failed" or "not_attempted" means no human was paged (typically channel_not_found because the approval-bot is not a member of the configured channel) \u2014 quote grant_id + notification_failure_reason and recommend manual escalation. poll_grant exists as an escape hatch for explicit re-checks but the autonomous flow does not need it.`,
+  'Request scoped, TTL-bounded AWS credentials for the current task. agent_id and run_id are optional \u2014 the broker fills them from the host MCP env (AGT_AGENT_ID / AGT_RUN_ID). source_context is optional but you SHOULD pass it whenever the request was triggered by an inbound channel message: extract { channel_type, channel_id, thread_ts? } from the `<channel>` tag in the conversation that triggered this. Slack: channel_type="slack", channel_id=tag\'s `channel`, thread_ts=tag\'s `thread_ts`. Telegram: channel_type="telegram", channel_id=tag\'s `chat_id`. Direct-chat: channel_type="direct-chat", channel_id=tag\'s `session_id`. Without source_context the resolution notification dead-ends in your direct-chat instead of threading back to the original conversation. Returns { grant_id, status, secret_ref?, expires_at?, denial_reason?, notification_status?, notification_failure_reason? }. status="active" means credentials are ready, use them now. status="denied" means the request was rejected (denial_reason explains). status="pending" means approval is still outstanding \u2014 DO NOT poll. The broker pushes the resolution to you via direct-chat the moment a human approves or denies, so save the grant_id, return control, and resume when the inbound message arrives. The notification body will include an "Original conversation:" line naming the channel/thread to reply in \u2014 complete the user\'s task there, not in direct-chat. Only check notification_status if you need to flag a setup issue to the user: "sent" means a human was paged; "failed" or "not_attempted" means no human was paged (typically channel_not_found because the approval-bot is not a member of the configured channel) \u2014 quote grant_id + notification_failure_reason and recommend manual escalation. poll_grant exists as an escape hatch for explicit re-checks but the autonomous flow does not need it.',
   requestAccessShape,
   async (args) => {
     try {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@integrity-labs/cloud-broker",
-  "version": "0.4.5",
+  "version": "0.4.6",
   "description": "Cloud Access Broker — MCP server that mints scoped, TTL-bounded cloud credentials per agent task. v1 ships AWS support (request_access, poll_grant, release_access, describe_scope, preview_request — STS AssumeRole under the hood); GCP, Azure, and Cloudflare land alongside in the same package as the broker grows.",
   "type": "module",
   "bin": {