In regulated environments, administrators need hard controls that cannot be bypassed by the agent or the user. The agent runs arbitrary code — instruction-level guardrails ("don't install plugins") can be ignored. A hard, declarative restriction in the CR provides a control surface that only the CR author (admin) can change.
The primary use case is blocking plugin installation in locked-down scenarios. Plugins can execute arbitrary code, access the network, and modify agent behavior. In a kiosk deployment (Scenario F), plugin installation must be impossible regardless of what the user or agent requests.
See https://github.com/redhat-et/claw-operator/tree/main/openspec/changes/add-restrictions
In regulated environments, administrators need hard controls that cannot be bypassed by the agent or the user. The agent runs arbitrary code — instruction-level guardrails ("don't install plugins") can be ignored. A hard, declarative restriction in the CR provides a control surface that only the CR author (admin) can change.
The primary use case is blocking plugin installation in locked-down scenarios. Plugins can execute arbitrary code, access the network, and modify agent behavior. In a kiosk deployment (Scenario F), plugin installation must be impossible regardless of what the user or agent requests.
See https://github.com/redhat-et/claw-operator/tree/main/openspec/changes/add-restrictions