Home / The model / The capabilities / send.endpoint.world
send.endpoint.world
Reach any host on the internet. Verb send, object network-endpoint, reach world, family network. Its effect is no: cannot be undone.
In 6 of 9 published shapes
| Deployment shape | Barrier there | Known by | Note | |
|---|---|---|---|---|
| ● | Claude Code (the CLI, on your own machine) | none (not a control) | derived | curl reaches the world unless something above the account stops it |
| ● | Claude Code (the CLI, on your own machine) | none (not a control) | derived | curl reaches the world unless something above the account stops it |
| ● | Claude Desktop (a desktop app with local tools) | none (not a control) | derived | |
| ● | A browser extension with broad host permissions | none (not a control) | documented | host permissions |
| ● | A scheduled job running as a service account | none (not a control) | derived | |
| ● | Actions runner (a hosted CI job) | none (not a control) | observed | github.com 200, pypi.org 200, example.com 200 - UNRESTRICTED egress, no proxy |
| Barrier | What stands in the way | Is it a control | |
|---|---|---|---|
| ● | none | nothing in the way | no |
| ◉ | expectation | a rule in prose, enforced by nobody | no |
| ◐ | setting | a switch the agent's own account can flip | no |
| ○ | boundary | enforced above the grant, out of the agent's reach | yes |
What the starting mandates say about it
| The mandate says | Which mandates |
|---|---|
| authorised | A CI job on a hosted runner |
| refused | Chat in the browser, nothing connected, A browser extension I installed, A scheduled job under a service account |
| unstated | A coding assistant on my machine, A coding assistant in a container on the web, The desktop app, with local tools switched on, Chat, with connectors switched on |
Unstated is not authorised. A mandate that never mentioned a capability did not authorise it, and the delta on every example page counts it as excess and says which kind it was.
What would move it to the fourth barrier
| What | What it costs | The barrier afterwards |
|---|---|---|
| route outbound traffic through an allow-list - the one control the hosted container already has, demonstrated rather than claimed | an hour, if you already have somewhere to put it | boundary |
This is a published reduction, not a recommendation. Whether it is worth doing depends on the assets and the consequences, which are not in this document and are not this site's to guess.