On November 12, Microsoft's status account reported that Microsoft 365 users in the Americas were having trouble reaching their Exchange Online mailboxes. Thirteen minutes later it said users in any region could be affected. Two and a half hours in, it said it hadn't found a recent change that lined up with the start of the impact. The next day it traced the incident to an issue from an earlier network capacity upgrade that surfaced after a recent network change, and called it a technical issue "not related to cyber or AI / agents". More than 26 hours after the first post, Microsoft still had no ETA for full recovery.
Most of us don't run a network that size, but plenty of us run a few VMs on AWS, GCP or Azure, and one network command is enough to cut one of them off. In Skyportal, SARA proposes the commands and you approve them. For the network commands you never want run from a chat, you can go a step further and put them on a deny list in your repo. Skyportal then refuses them before an approval card is shown, and no allow list entry or Auto-approve gets them through.
What one command can do to a cloud VM
Skyportal reaches your VM over SSH, the same way you do, so whatever breaks SSH for you breaks it for SARA too. A few commands that do it:
ip link set eth0 downtakes the network interface down, and the SSH session that ran it goes with it. On many AWS and GCP images the interface isens5orens4, with the same result.ip route del defaultremoves the default route. The VM can still reach its own subnet, but replies to your laptop have no way out.iptables -Fdeletes every rule and leaves each chain's default policy as it was. If the INPUT policy is DROP, the VM now drops everything, your SSH connection included.netplan applywith the wrong address or gateway in the config leaves the interface with settings it can't use.
The way back is the provider's serial console (EC2 Serial Console, the serial console on Compute Engine, Azure Serial Console) or a reboot, if the change wasn't saved anywhere that survives one. For netplan there is a safer habit: netplan try applies the config and rolls it back after 120 seconds unless you confirm it.
What SARA does with a network command today
With the default settings, none of these run on their own. When SARA proposes one and no allow list covers it, the chat shows an approval card titled "Needs your approval", with the exact command and the host it will run on, and nothing happens until you answer.
A few things change that, and it's worth knowing them before an incident. The card's Always allow button saves the command's first word to that host's allow list. Click it on ip addr show and the host now allows ip, so a later ip route del default runs without a card. A host labeled Production blocks the commands Skyportal knows as destructive, such as rm or systemctl restart networking. ip, iptables and netplan aren't on that list, so on a Production host they get an approval card rather than a refusal.
Write the deny list
The deny list lives in the repo, in .skyportalai/settings.json at its root. Each entry is a run_command(...) rule with a pattern, where * stands for any text. This file denies the four commands above, with and without sudo, since on a VM where you log in as a regular user they only work with it:
{
"permissions": {
"deny": [
"run_command(ip link set *)",
"run_command(sudo ip link set *)",
"run_command(ip route del *)",
"run_command(sudo ip route del *)",
"run_command(iptables -F*)",
"run_command(sudo iptables -F*)",
"run_command(netplan apply*)",
"run_command(sudo netplan apply*)"
]
}
}
A rule has to match a whole command, not just its start. Skyportal splits chained commands at &&, ||, ; and |, and blocks the whole line if any part matches. It doesn't look inside sudo, bash -c or $(...), which is why each rule above has a sudo twin. A rule also covers only what it spells out: run_command(iptables -F*) doesn't catch iptables -t nat -F, while run_command(iptables *) catches every iptables command, reads like iptables -L included.
Each list holds up to 50 entries of up to 500 characters. If the file is broken, say a missing bracket or an entry that isn't run_command(...), Skyportal doesn't treat it as "no rules": every command asks for approval, and the card says why. An old .skyportal/settings.json gets the same treatment, with a message telling you to rename it to .skyportalai/settings.json. The file can hold an allow list too, and a deny match wins over every allow.
Let SARA clone the repo
Repo rules apply when the chat has that repo selected on that VM, and a repo gets selected when SARA clones it. Ask SARA to clone it with git clone or gh repo clone. When the clone finishes, the chat says which repository it selected, and from then on Skyportal checks every command on that VM against the file. A private repo needs the GitHub token from the clone post, and the VM needs python3 for the indexing that follows the clone.
Skyportal reads the file once per chat, from the clone on the VM, so after you change it, pull on the VM and start a new chat. A new chat on that VM selects the repo SARA cloned there most recently, as long as that was in the last 7 days; after that, ask SARA to clone it again. A repo you cloned yourself is never selected, so its file doesn't apply. The rules also belong to that one VM: in a chat that spans several hosts, they cover only the host where the repo lives.
What happens when SARA tries a denied command
Nothing runs, and no card appears. In the web chat, the command's output reads Command blocked by repo deny list (matched rule: 'run_command(sudo ip link set *)'), next to "Blocked on" with the host name and the title "Blocked by the repo deny list". The CLI prints the same title on a blocked line. SARA gets the refusal back, and anything else it proposes goes through the usual approval card.
The check comes before approvals, so nothing after it can let the command through: a one-time approval, an allow list entry (including one saved with Always allow) and Auto-approve are all checked later. When a command fans out to several hosts, Skyportal checks each host, and one blocked host stops the whole run before anything executes. To change the rules, edit the file. The Settings link on the card opens Agent Settings, which is where the host allow lists live, not the repo rules.
Get started
The deny list works with any repo SARA clones, public or private. Cloning a private repo needs the GitHub integration, which is part of the Pro plan. Sign up, connect your VM over SSH, add .skyportalai/settings.json to the repo and ask SARA to clone it.