Test the rule before your agent acts.

Set a payment limit in Policy Builder. Try requests on either side of the threshold. See when the policy permits submission and when treasury must review it.

Read the decision contract

Policy Builder

Payment limitsVersion 3

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

Approval threshold €250,000

€0€500,000

Policy outcomeRequire approval

The amount exceeds the delegated limit. Hold the submission for treasury review.

Sample request · amount only

Four outcomes. An explicit next step.

The KLA Policy Engine evaluates the action with its identity, permissions and business context. The outcome tells the connected runtime what to do next.

Allow: The action satisfies the applicable policy and can proceed.
Warn: The action can proceed with a recorded warning for review.
Require approval: The action pauses for an authorized reviewer in Decision Desk.
Block: The governed action stops before the tool is called.

The simulation isolates one rule. The connected runtime must enforce the final decision before it calls the tool.

Keep the version that made the decision.

A decision is useful to a reviewer when it retains the context and policy version that produced it.

Action context

What it contains

Agent, tool, requested action and supplied business attributes

Question it answers

What the policy evaluated

Policy decision

What it contains

Policy identifier, version, outcome and reason codes

Question it answers

Why the action proceeded, paused or stopped

Linked outcome

What it contains

Decision Request, review outcome and captured tool response

Question it answers

What happened after the decision

Record	What it contains	Question it answers
Action context	Agent, tool, requested action and supplied business attributes	What the policy evaluated
Policy decision	Policy identifier, version, outcome and reason codes	Why the action proceeded, paused or stopped
Linked outcome	Decision Request, review outcome and captured tool response	What happened after the decision

Schemas and examples.

Use the schemas and worked examples to review the integration and evidence requirements.

See how an approval is resolved

Start with a rule your team already uses.

Bring a payment limit, a restricted destination or a tool permission. Choose sample requests that should pass, pause and stop.

Talk to KLA