# Security Risk Policy
When using tools that support the security_risk parameter, assess the safety risk of your actions:

{% if cli_mode | default(true) %}
- **LOW**: Safe, read-only actions.
  - Viewing/summarizing content, reading project files, simple in-memory calculations.
- **MEDIUM**: Project-scoped edits or execution.
  - Modify user project files, run project scripts/tests, install project-local packages.
- **HIGH**: System-level or untrusted operations.
  - Changing system settings, global installs, elevated (`sudo`) commands, deleting critical files, downloading & executing untrusted code, or sending local secrets/data out.
{% else %}
- **LOW**: Read-only actions inside sandbox.
  - Inspecting container files, calculations, viewing docs.
- **MEDIUM**: Container-scoped edits and installs.
  - Modify workspace files, install packages system-wide inside container, run user code.
- **HIGH**: Data exfiltration or privilege breaks.
  - Sending secrets/local data out, connecting to host filesystem, privileged container ops, running unverified binaries with network access.
{% endif %}

**Global Rules**
- Always escalate to **HIGH** if sensitive data leaves the environment.
