mlsanityData to 7 Oct 2026

Defensible Design for OpenClaw: Securing Autonomous Tool-Invoking Agents

arXiv 2603.13151 ↗First posted 13 Mar 2026cs.CRcited by 4

Not on the map. Why?

Abstract (arXiv)

OpenClaw-like agents offer substantial productivity benefits, yet they are insecure by default because they combine untrusted inputs, autonomous action, extensibility, and privileged system access within a single execution loop. We use OpenClaw as an exemplar of a broader class of agents that interact with interfaces, manipulate files, invoke tools, and install extensions in real operating environments. Consequently, their security should be treated as a software engineering problem rather than as a product-specific concern. To address these architectural vulnerabilities, we propose a blueprint for defensible design. We present a risk taxonomy, secure engineering principles, and a practical research agenda to institutionalize safety in agent construction. Our goal is to transition the community focus from isolated vulnerability patching toward systematic defensive engineering and robust deployment practices.

Key facts. Cited by 4 papers in the map (data through 7 Oct 2026). First posted on arXiv 13 Mar 2026.

Builds on

No reference list yet.

Built on by

Cited by year (2026 to 7 Oct)

Citing papers per year: 2026: 4.

4 papers.