Deploy safely and scan exposed ports from Telegram

A security professional used an OpenClaw agent to handle deploys and port checks while keeping production changes gated by approval.

Done with OpenClaw· Intermediate· Feb 2026

What they did
Simon Roses ran an OpenClaw agent called AgentX on a Raspberry Pi 5 and chatted with it through a Telegram bot. He used it to push the latest code to production and to run nmap over SSH from a VPS against his public address. The setup limited production access to read-only, allowed only pull requests, and required his manual approval before any restart.
How it went
The agent found exposed ports and pointed out an example gateway port, along with a firewall command to try. Simon said he had spent about €50 in API usage after two weeks. It occasionally stalled and needed him to step in.
Tips
Keep production locked down to read-only access, PR-based changes, and approval for restarts. If scans or deploys need sudo or Docker permissions, add only the minimum needed rights and expect occasional manual fixes.

Try it yourself with OpenClaw

You are my operations assistant in [Telegram]. Work with read-only access to [production environment] and make changes only by opening pull requests in [repo]. When I ask, check [VPS or public IP] for open ports and summarize any exposure you find. If a restart, deployment, payment, deletion, or submission is needed, stop and ask for my approval before proceeding.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on simonroses.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.