Policy · critical
No exec after secret read
Block Bash execution after reading files classified as secrets (.env, .pem, .key, credentials, pgpass, netrc). The kyvvu-claude mapper automatically classifies these files with data.classification: secret.
The policy
A few lines of YAML in your repository.
Part of Claude Code safety. Assign the pack, or copy this policy into a manifest of your own.
- Verdict
- Critical: the step is blocked before it runs, and an incident is opened.
- Checked
- Before every step, against everything the agent did earlier in the task.
- Rule
- tainted_path_block
- name: "No exec after secret read" description: | Block Bash execution after reading files classified as secrets (.env, .pem, .key, credentials, pgpass, netrc). The kyvvu-claude mapper automatically classifies these files with data.classification: secret. Taint is permanent within the task. Start a new Claude Code session (or /clear) to reset. rule_type: tainted_path_block params: taint_kind: step.resource taint_verb: GET taint_property_filter: data.classification: secret target_kinds: ["step.exec"] severity: critical enforcement_point: step_executionWhy it matters
Taint is permanent within the task. Start a new Claude Code session (or /clear) to reset.
How the rule works
tainted_path_block: If any prior step matches the taint pattern, certain downstream steps are blocked. The taint is permanent within a task; no gate can clear it.
taint_kind:step.resource. Action kind of the step that taints the task.taint_verb:GET. Only steps with this verb taint.taint_property_filter:{"data.classification":"secret"}. Only steps whose properties match all entries taint (e.g. data.classification: pii).target_kinds:["step.exec"]. Action kinds the rule applies to (e.g. step.resource, step.exec, step.message); other steps pass.
In these packs
- Claude Code safety, version 1.0.5
From Kyvvu's open policy library at github.com/Kyvvu/manifests, Apache 2.0.
Next
Watch it decide.
In your browser
Try it in the playground
The policy is loaded. Add the steps your agent takes and watch the engine decide, step by step.
On your machine
Five minutes, no account
kyvvu try runs a demo agent against the bundled baseline. Then assign this pack from the dashboard or the CLI.
For security teams
See it on your agents
A 30-minute demo on the agents you actually run, with the policies that fit them.