Kyvvu

Policy · critical

Forbid credential read followed by external send

Blocks a step.message after any step.credential GET in the task history. A credential write does not taint the path. This prevents credential exfiltration via indirect prompt injection.

The policy

A few lines of YAML in your repository.

Part of Data exfiltration guard. 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: "Forbid credential read followed by external send"  description: |    Blocks a step.message after any step.credential GET in the task    history. A credential write does not taint the path. This prevents    credential exfiltration via indirect prompt injection.  rule_type: tainted_path_block  params:    taint_kind: step.credential    taint_verb: GET    target_kinds: ["step.message"]  severity: critical  enforcement_point: step_execution

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.credential. Action kind of the step that taints the task.
  • taint_verb: GET. Only steps with this verb taint.
  • target_kinds: ["step.message"]. Action kinds the rule applies to (e.g. step.resource, step.exec, step.message); other steps pass.

In these packs

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.