This page was translated from Dutch with AI.

What my agent is allowed to fix on my server by itself

In my previous article I shared how Tom Verheyden forwarded me a warning about new security leaks. And how I then asked my Webmaster agent to monitor and update my servers by itself from now on. After about twenty-five minutes it was done. It had built two skills and one automation that runs them twice a day. Do you want to start yourself? Then copy the starting prompt at the bottom of this article, and let your agent make an inventory of your own server first.

Today I want to show you how that works. I am leaving out my own settings, it is about the principle. And I think that principle is useful for you too. Especially if you have put something online yourself after a workshop on Claude, agents or vibe coding.

Cartoon

The diagram

My agent gave me a small diagram at the end. I have translated it here and made it a bit more general.

The diagram: an automation runs the watcher, the fixer decides according to the mandate
The diagram: an automation runs the watcher, the fixer decides according to the mandate

So the first skill only looks. It compares what is running on my servers with what has been reported in terms of leaks. Then the second skill decides per problem whether it is allowed to solve it by itself. If it is allowed, it does it and writes down what it has done. If it is not allowed, I get a proposal.

Not every source carries the same weight

In my prompt I had asked to compare reliable sources. My agent actually put those sources into three layers, and I thought that was very sensible.

The first layer is the creators themselves. The people behind Node.js or PHP, the creators of the operating system and the official databases with leaks in open-source packages. Only those sources are allowed to confirm that a version has a leak, and which version solves it.

The second layer is independent sources that determine the urgency. For example the list of leaks that are actually being exploited right now. Or the advice of the CCB, the Belgian centre for cybersecurity. If a leak is listed there, it moves to the front.

The third layer is news, search results and emails like the one from Tom. Those only count as a tip. Based on that, nothing ever just changes on my server. I actually found that quite funny, because it was exactly such an email that set the whole exercise in motion.

Keep reading for free

Register free with your e-mail address and read on. Your account opens the free articles in the learning space; the rest is for subscribers, from Learn Plus up.

Already registered? No account yet?

QR code of this page

coachsteff.live/en/wat-mijn-agent-zelf-mag-oplossen

Scan with your phone to open the page.