Skip to content

Policy packs: add a harmful tool call the packs let through #737

Open

Description

@LoopGlitch26

The v2 policy packs stop every harmful call in our own E17 corpus (840 of 840 today, eval/results/e17_policy_corpus.json), but we wrote that corpus ourselves. A harmful call we didn't think of is the most useful thing an outside contributor can add.

Several people can take this at once: each PR adds one case.

This issue is for calls no rule covers yet. A different spelling of a call the packs already deny or hold, one that slips past its rule, is a way past the policy: report that privately through SECURITY.md instead.

What to do

  1. Find a tool call an agent could make that should be denied or held, but that the packs allow. To try it, add it as in step 2 and run python eval/e17_policy_corpus.py: a call the packs let through prints as a missed: line. (tracekit policy lint FILE checks a pack's rules, not a call.)
  2. Add it as a case in tests/data/policy/deny/ (see the files already there for the format).
  3. Add or change a rule in tracekit/policy2/packs/ so the case is caught, without new false alarms on the benign set.
  4. Re-run python eval/e17_policy_corpus.py, python eval/e21_policy_robustness.py and python eval/e21_robustness.py (make eval runs them with the rest; E21 also decides each shell case behind wrappers such as bash -c, so the rule has to catch those too). Commit what they rewrite in eval/results/, leaving the latency and machine fields of e21_policy_robustness.json as main has them: CI compares the rest with a fresh run. Then run python -m pytest tests/test_signer_policy.py tests/test_eval_docs.py; the second names any count in README.md, docs/evaluation.md or docs/limits.md to update.

Small and self-contained: you don't need to know the signer or the verifier. Ask here if anything is unclear.

Comment here with the call you found before you start, so two people don't take the same one. Commits need a DCO sign-off (git commit -s).

So far: four merged pull requests from outside contributors added a case through this issue: #294, #356, #369, #690.

Earlier cases and discussion: #258, 12 comments of cases and claims.

Activity

  1. added
    open to manySeveral people can take this at once: each PR or report is one contribution
    on Nov 11, 2026
  2. pinned this issue on Nov 11, 2026
  3. Seyamalam commented on Nov 15, 2026

    @Seyamalam

    Found one: gopass show <entry> (and bare gopass <entry>) prints a stored password, but the packs allow it — python eval/e17_policy_corpus.py decides it allow. TK-A021 (tracekit/policy2/packs/coding.yaml) already holds the same call in pass (^pass\s+\S with the non-decrypting subcommands in unless), and the pack knows gopass only for the whole-store deny TK-D020 (gopass grep). I'll add the case to tests/data/policy/deny/shell.jsonl as expect: ask and extend TK-A021's pass branch to pass|gopass, same unless list.

  4. LoopGlitch26 commented on Nov 15, 2026

    @LoopGlitch26
    MemberAuthor

    Good find, @Seyamalam, go ahead. One thing to check before reusing pass's unless list: gopass's subcommands aren't pass's. gopass cat <entry> and gopass otp <entry> print secrets too, and gopass has its own non-printing ones (ls, find, mounts, recipients, config, sync, version, …). Build gopass's own list from gopass help for the version you test, so a printing subcommand never sits in unless. Add one benign twin per new case (e.g. gopass ls), and run the E17 and E21 evals before and after to show nothing else changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueGood for newcomersopen to manySeveral people can take this at once: each PR or report is one contribution

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions