Por que as barreiras de segurança são importantes

OpenClaw runs on your hardware with real reach. That power is the point, but it is also why guardrails matter from day one. 🛡️

Your assistant can touch your files, your shell, and your scripts. This full system access is what makes it useful, and what you must contain.

OpenClaw does not just answer; it acts. It can send email, fill web forms, and run commands. Anyone who reaches it can act through it too.

You talk to OpenClaw from chat apps, so each connected channel is a door into your machine. Every open door needs a lock you control.

OpenClaw leans on two simple guardrails: allowlisting who can message it, and requiring a mention before it responds in groups.

An allowlist means only senders you name can reach the assistant. Everyone else is ignored, so a stray message cannot trigger an action.

In busy group chats, requiring a mention stops OpenClaw from reacting to every message and only acting when it is clearly addressed.

Because OpenClaw is local-first and self-hosted, your data and actions stay on your own hardware instead of a shared cloud service.

Treat every channel and sender as something to justify. The least exposure mindset keeps your assistant powerful but hard to misuse.

You enforce guardrails in the config at ~/.openclaw/openclaw.json, the JSON5 file that shapes how OpenClaw behaves.

When you want depth, the /gateway/security docs explain how to harden a deployment that has this much reach. 📚

OpenClaw is powerful because it has full system access and acts for you. Guard it with allowlists and mentions, set in your config. ✅