I'm a backend engineer on Atlassian's Rovo Agents team. A few weeks ago, OpenAI acquired the OpenClaw project and I started thinking about what happens when agents get broad access to your data with no permission layer.
Six days later, Summer Yue (Director of Alignment at Meta) posted about her OpenClaw agent deleting 200+ emails while ignoring her stop commands. The root cause was context window compaction dropping her safety instruction. The agent kept working. It just lost the part where it was supposed to ask first.
Shield is a plugin that hooks into OpenClaw's tool system and intercepts every action before it executes. Permissions are enforced outside the model's context window, so they can't be compressed away. You set what each agent can access (read/write/execute per service), and anything outside those boundaries gets blocked or routed through an approval workflow with time-limited grants.
TypeScript, open source, MIT licensed. The plugin, dashboard, and docs are all live. Happy to answer questions about the architecture or how the OpenClaw Plugin API integration works.
verdverm•28m ago
OpenClaw is a security nightmare, there are much better frameworks out there that don't need these afterthought addons. There are also dozens and dozens of this same project in /show the last month+ now.
Please tell me you are not using OpenClaw with Rovo
What you are talking about is called "the lethal trifecta", worth looking up and understanding if you are not familiar.
rachelle-r•1h ago
verdverm•28m ago
Please tell me you are not using OpenClaw with Rovo
What you are talking about is called "the lethal trifecta", worth looking up and understanding if you are not familiar.