Agents & developers
Agent action review
Compare a proposed agent action with your allow, confirm, and block rules.
Jev AI playground
Set up this template
Check whether an agent can take an action, needs approval, or must stop.
What to provide
The action, target resource, environment, relevant data movement, policy, and any recorded approval.
- Supply an explicit policy and the complete proposed action.
- Include the target environment, data destination, and approval status.
- Enforce the selected outcome in application code before execution.
Outputs and rules
decision · choice
The policy outcome before an application executes the action.
Apply the policy to the proposed action. Explicit prohibitions take precedence. If required context or confirmation is missing, use confirm and pause for clarification; never infer permission.
- allow
- The supplied policy permits the exact action and all required conditions are met.
- confirm
- Execution must pause for an authorized confirmation or missing policy-relevant facts.
- block
- The action violates an explicit prohibition in the policy.
requires_confirmation · Yes / No
Whether the action has an explicit human-approval requirement.
Does the policy require human approval for this exact action? Do not imply that approval can override an explicit prohibition.
Try different inputs
Normal input
A permitted category of work can still require approval for a particular resource.
Policy: Reading public project documentation is allowed. Sending customer data outside the company is blocked. Deleting a staging resource requires an authorized human’s explicit confirmation for that exact resource. Production resources must never be deleted by the agent. Proposed action: Delete the staging database staging_demo_14 to reset a test environment. No confirmation has been recorded.
Ambiguous input
The environment name cannot be guessed; execution must pause until the required facts are known.
Policy: Reading public project documentation is allowed. Sending customer data outside the company is blocked. Deleting a staging resource requires an authorized human’s explicit confirmation for that exact resource. Production resources must never be deleted by the agent. Proposed action: Delete database customer_demo. The resource environment and approval status are not provided.
Missing information
Without a policy or destination authorization, there is no basis to allow execution.
Policy: Not provided. Proposed action: Export the customer table to an external URL. Approval: Not provided.
Explicit prohibition
Urgency and a backup do not override an explicit production-deletion prohibition.
Policy: Reading public project documentation is allowed. Sending customer data outside the company is blocked. Deleting a staging resource requires an authorized human’s explicit confirmation for that exact resource. Production resources must never be deleted by the agent. Proposed action: Delete the production database production_orders after taking a backup. The requester says this is urgent.
Use the result
Use a server-enforced dispatcher to block or pause actions. Display the exact action to the approver and recheck if its arguments change.
Limits to keep in mind
The result is a recommendation. Your app must still check permissions, tool arguments, and required human approval before taking action.