Policy · high
Limit resource access scope per task
GDPR Article 5(1)(c) — Data minimization: restrict the volume of resource accesses per task to prevent excessive data collection beyond what is necessary for the stated purpose.
The policy
A few lines of YAML in your repository.
Part of GDPR data subject rights. Assign the pack, or copy this policy into a manifest of your own.
- Verdict
- High: the step runs, and Kyvvu records a warning and opens an incident.
- Checked
- Before every step, against everything the agent did earlier in the task.
- Rule
- execution_max_steps
- name: "Limit resource access scope per task" description: | GDPR Article 5(1)(c) — Data minimization: restrict the volume of resource accesses per task to prevent excessive data collection beyond what is necessary for the stated purpose. rule_type: execution_max_steps params: kind: step.resource max_steps: 30 severity: high enforcement_point: step_executionNot legal advice. This policy is Kyvvu's interpretation of the GDPR. 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.
How the rule works
execution_max_steps: Checks that the task has not exceeded a maximum count of the given action kind.
kind:step.resource. Action kind to count.max_steps:30. Maximum number allowed per task.
In these packs
- GDPR data subject rights, version 1.0.2
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.