Product / Rules
Review an agent action before it exceeds the brief.
Compare proposed actions with an explicit authority contract covering paths, commands, hosts, and budget.
- Allowed scope
- Account settings files
- Proposed action
- Change the production schema
- Decision
- Approval required
- Next step
- Ask the authorized owner
Why use Rules?
Permission to fix one feature should not be mistaken for permission to change production or unrelated code. Make the allowed work explicit.
Keep scope inspectable
See the rule behind an allow, deny, unknown, or approval-required result.
Expose missing authority
Uncovered actions remain visible so someone can resolve the boundary.
Make approval specific
Review the proposed action and its scope before granting additional authority.
How Rules fits your work
- 01
Define the boundary
Supply the authority contract for the task.
- 02
List proposed actions
Include the actual paths, commands, or hosts the agent intends to use.
- 03
Review the decisions
Resolve denied, unknown, or approval-required actions in your execution workflow.
What to know before you start
Evaluating a contract is not a universal sandbox. Your execution system must enforce the returned decisions.
Use your workspace or a compatible agent connected through MCP. Read the connection guide.