Skip to content

Warn users about suspicious policies #21596

@jacob314

Description

@jacob314

We need to warn users if their policy has obviously unwise things.
A few times I've accidentally auto-approved editing files and rm.

An average user will have no idea what went wrong if

[[rule]] toolName = "run_shell_command" decision = "allow" priority = 100 commandPrefix = [ "rm" ]

if in their policy. To mitigate this I'd suggest we warn if the default policy allows rm or editing files.
If users want to approve rm in their policy when in accept-edits mode that is fine.

Similarly the UI option to approve RM for the session should only offer approving it for accept edits mode although even that might be too far as even when accepting edits you generally don't want the model to rm -rf to remove all the tests it just added.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/enterpriseIssues related to Telemetry, Policy, Quota / Licensingeffort/small1 day or less: trivial logic, UI adjustments, docskind/bugkind/customer-issueIssues that were reported by customerspriority/p3Backlog - a good idea but not currently a priority.status/bot-triagedstatus/need-informationworkstream-rollupLabel used to tag epics and features that are associated with one of the three primary workstreams🔒 maintainer only⛔ Do not contribute. Internal roadmap item.

    Type

    No fields configured for Task.

    Projects

    Status
    Closed

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions