Kyvvu

Policy · critical

Market data read taints downstream trade execution

DORA Article 9 — ICT risk management: once market data is read from an external source, automated trade execution (step.resource POST) is permanently blocked for the remainder of the task. This prevents algorithmic decisions based on potentially manipulated or stale market data from being executed without human review.

The policy

A few lines of YAML in your repository.

Part of Financial services: DORA and MiFID II. 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: "Market data read taints downstream trade execution"  description: |    DORA Article 9 — ICT risk management: once market data is read    from an external source, automated trade execution (step.resource    POST) is permanently blocked for the remainder of the task. This    prevents algorithmic decisions based on potentially manipulated or    stale market data from being executed without human review.    This is a path-dependent policy: the same POST operation is allowed    when no market data has been read, but blocked after a market data    read enters the task history. A stateless per-call check cannot    enforce this.    IMPORTANT: Replace market-data.example.com with your actual market    data provider domain.  rule_type: tainted_path_block  params:    taint_kind: step.resource    taint_verb: GET    taint_property_filter:      target.host: market-data.example.com    target_kinds: ["step.resource"]    target_verb: POST  severity: critical  enforcement_point: step_execution
Not legal advice. This policy is Kyvvu's interpretation of DORA and MiFID II. It isn't reviewed or endorsed by a regulator, and using it doesn't on its own make you compliant: it gives you technical controls, and a record that they ran, to support your compliance work.

Why it matters

This is a path-dependent policy: the same POST operation is allowed when no market data has been read, but blocked after a market data read enters the task history. A stateless per-call check cannot enforce this.

IMPORTANT: Replace market-data.example.com with your actual market data provider domain.

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: {"target.host":"market-data.example.com"}. Only steps whose properties match all entries taint (e.g. data.classification: pii).
  • target_kinds: ["step.resource"]. Action kinds the rule applies to (e.g. step.resource, step.exec, step.message); other steps pass.
  • target_verb: POST. Only apply to target steps with this verb (e.g. GET, POST, DELETE).

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.