Runtime security
The sandbox
Section titled “The sandbox”Sessions run in disposable, isolated runners inside the org’s environment. The runner network has no direct internet:
- MCP traffic goes through the in-API mcp-proxy — connector secrets never enter the sandbox.
- Everything else leaves through the egress proxy: an allowlist derived from the org’s registered connectors (plus explicit extras), with every call logged — host, method, bytes out/in, allow/deny decision.
Your laptop and network are never part of a run.
Data classes
Section titled “Data classes”Every connector is labelled external / internal / commercial / personal.
Sessions marked result may leave the workspace only admit connectors up to the
org’s configured threshold — the check runs server-side at session creation and
is recorded as a policy event.
Monitoring
Section titled “Monitoring”Security → Monitor shows live sessions, open alerts and the egress ledger (where data went, how much, allowed or blocked) over 1h/6h/24h windows.