How KLA works
Check the policy before the tool call.
An agent requests a payment. KLA evaluates the amount against your operating rule. The connected execution path can proceed, pause for review or stop before it reaches the payment tool.
Payment approval rule
- When
An agent submits a payment
- If
Amount exceeds €250,000
- Then
Require approval from Treasury reviewer
This example isolates one amount rule. Other policies can also affect the final decision.
Try a sample request
Policy outcomeRequire approval
The amount exceeds the delegated limit. Hold the submission for treasury review.
Try both payment amounts. The example evaluates one rule; the final decision can also depend on identity, permissions and other applicable policies.
The decision tells the runtime what to do.
KLA returns one of four outcomes. The integration must apply it before calling the tool, including the hold required for human approval.
- Allow
- The action can proceed.
- Warn
- The action can proceed with the warning recorded.
- Require approval
- Hold the action for an authorized human decision.
- Block
- Stop the proposed action.
Connect one operation, then test its failure paths.
A checkpoint needs to stop or hold the operation. Telemetry reports what happened; enforcement requires the tool call to respect the decision.
Confirm the supported integration, supplied policy context, reviewer permissions and captured events. Coverage follows that connected action path. Include unavailable dependencies, rejected approvals and tool failures in the evaluation.
Review supported integration paths- 1
Define the action and its policy
Identify the operation, the context it needs, the applicable rule and the person responsible for exceptions.
- 2
Connect the execution boundary
Place the supported integration at the tool call or operation that must respect the policy decision.
- 3
Apply the decision
Permit, warn, hold for an authorized reviewer or block the action according to the policy outcome.
- 4
Review the connected record
Inspect the request, applicable policy, human decision and resulting action in the execution record.
Open the detail your next review needs.
Resolve a waiting request, investigate an executed action or inspect an evidence sample. Each surface answers a different question about the workflow.
Lineage Explorer
Follow the action through its recorded decisions and outcome.
Explore Lineage ExplorerBring one agent and the tools it uses.
We can map the policy checks, review steps and evidence needed for an evaluation.