Register a server
In Workspace → MCP & integrations, a company owner can register a public HTTPS MCP endpoint, discover tool schemas and remove the server. Endpoint validation rejects private, loopback, link-local and reserved IP addresses. DNS answers are pinned for the outbound connection, and redirects are revalidated.
Tool state
Legacy company-scoped connections remain discovery-only. The profile connections panel supports anonymous or encrypted bearer-authenticated public HTTPS servers, paginated discovery, explicit read-tool grants, and user-triggered tools/call imports into company evidence. Rediscovery resets grants. The worker uses selected imported evidence rather than invoking tools autonomously. Per-agent grants, OAuth, stdio and external write execution are not implemented.
Design for a future adapter
Map each tool to a narrow action and risk level. Add credentials, authorization, execution and audit behavior only after the policy boundary is defined. For actions that alter external systems, make retries idempotent and keep an approval point where needed.