Approving what agents may reach and use: the allowlist in the console, and approved skills, plugins and MCP servers #494

Open
opened 2026-11-11 17:44:38 -05:00 by cmoriarty · 0 comments
Owner

What happens
Inside a step's sandbox (braid#203) the internet is open and the private network is closed, except the endpoints listed in the stack variable OSF_EGRESS_ALLOW. Changing it means editing the stack and redeploying. And a run's agents are offered only the worktree's own skills and Braid's one browser server: there is no way to approve a skill, a plugin or an MCP server for them.

What we want (the owner, 2026-11-11: "first-class access to the internet, and to approved internal APIs, MCPs, Skills, Plugins etc, but it should not be able to just roam the local network")

  • The allowlist as a setting in the console, read when a sandbox is made.
  • A list of approved MCP servers, attached to runs, each with the endpoints it needs opened.
  • Approved skills and plugins offered to agents. To design: where they live, and what a run pays in tokens for each.

Done when
An internal endpoint approved in Settings is reachable from the next run's steps without a deploy, and an approved MCP server's tools reach the agents the setting names.

**What happens** Inside a step's sandbox (braid#203) the internet is open and the private network is closed, except the endpoints listed in the stack variable `OSF_EGRESS_ALLOW`. Changing it means editing the stack and redeploying. And a run's agents are offered only the worktree's own skills and Braid's one browser server: there is no way to approve a skill, a plugin or an MCP server for them. **What we want** (the owner, 2026-11-11: "first-class access to the internet, and to approved internal APIs, MCPs, Skills, Plugins etc, but it should not be able to just roam the local network") - The allowlist as a setting in the console, read when a sandbox is made. - A list of approved MCP servers, attached to runs, each with the endpoints it needs opened. - Approved skills and plugins offered to agents. To design: where they live, and what a run pays in tokens for each. **Done when** An internal endpoint approved in Settings is reachable from the next run's steps without a deploy, and an approved MCP server's tools reach the agents the setting names.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#494
No description provided.