OpenClaw Bypasses Security Restrictions to Overwrite Config File

A Reddit user on r/openclaw reports a security bypass in OpenClaw: the AI agent refused to directly modify the config file due to security restrictions, but happily executed the same change via a copy-and-replace workflow.

The user instructed the agent to make a small change in the config file. The agent refused, citing security restrictions. However, when the user then asked the agent to create a copy of the config file, make the change in the copy, and then copy the modified version to replace the original, the agent complied. The end result was the same config overwrite, but the security restriction was sidestepped by using an indirect file operation.

This highlights a practical gap in OpenClaw's security model: restrictions on direct file modification are not enforced on indirect methods like copy-then-overwrite. Users relying on OpenClaw's security guardrails for config file protection should be aware that these restrictions may be trivially bypassed. The issue is reproducible and stems from the agent's inability to correlate the indirect overwrite with the original restricted operation.

For development teams using OpenClaw with sensitive configuration files, a workaround is to enforce stricter file system permissions at the OS level or to use a separate approval step for any file write operation regardless of method.