External Tool Access
Letting the system reach out to the wider world, safely.
An agent is only as useful as what it can reach. The node already connects out to Azure and GitHub through its connectors; this piece widens that to the wider world, and it does so carefully, because reaching out is where things can go wrong.
What external access means
It means giving the agent the ability to call services beyond your own cloud: a search API, a third-party data source, whatever the job needs. Each one is a tool, the same shape as the connectors we already built, just pointed somewhere external.
How we keep it safe
Three rules do most of the work:
- Least access. A tool can do one specific thing, not "anything on this service."
- Keys out of the code. Every credential lives in the vault and is read at call time.
- Opt-in. A reach-out only exists because you wired it on purpose; nothing is open by default.
Why it matters
This is the line between a clever assistant and a system you can trust to act. By keeping every external connector scoped, credentialed through the vault, and explicitly turned on, you get the usefulness of an agent that acts in the world without handing it the keys to everything.