← Back to Home
Policy Firewall

Your rules.Enforced.

Turn plain-language intent into reviewed, deterministic policies for configured tool calls.

See Policy Firewall
GRANULAR POLICIES. PRECISE CONTROL.

Control the details.
Not just the tool.

Set conditions on amounts, recipients and destinations. Limit call volume. Preview decisions in shadow mode before enforcing.

Policy precision
ONE RULE. EXPLICIT CONDITIONS.
YOUR INSTRUCTION
“Hold refunds above $500 for review.”
APPLIES TOSupport agents · refund.create
WHEN
Actionequals
refund.create
AND
Amountgreater than
$500
THEN
Decision
Hold for review
Review drafted conditions before activating a policy.
TRY A REQUEST

See exactly what matches.

INCOMING TOOL CALLrefund.create
amount
$640
currency
USD
CONDITION MATCHEDHold for review

$640 exceeds the configured $500 boundary.

Illustrative policy examples · Non-matches follow other matching rules or the configured fallback.
01 / PARAMETERS

Specify the action.

Check amounts, recipients, destinations and other request attributes.

02 / RATE LIMITS

Bound the volume.

Set limits on how often agents can use configured tools.

03 / SHADOW MODE

Observe before enforcing.

Record the verdict a rule would produce before applying it to live requests.

PII · PCI · PHI DETECTION & REDACTION

Find sensitive data.
Control what gets through.

Detect personal, payment and health information. Apply your policy to redact, mask, pseudonymize or drop sensitive values before they reach the agent.

01 / PII

Personal information

Identify personal details such as names and Social Security numbers.

NAME DETECTEDAlex MorganPerson 1Pseudonymized
02 / PCI

Payment information

Recognize payment card data and limit what the agent receives.

CARD NUMBER DETECTED4242 4242 4242 4242•••• •••• •••• 4242Masked
03 / PHI

Health information

Find sensitive health identifiers, including medical record numbers.

MEDICAL RECORD DETECTEDMRN 58216[REDACTED]Redacted

Illustrative transformations · Detection and treatment depend on configured policies. Name detection uses optional named-entity recognition.

STRUCTURED & UNSTRUCTURED DATA

Different formats.
The same policies.

All the policies you configure apply across structured and unstructured data—including how PII, PCI and PHI are handled.

Your configured policies
  • Access & permissions
  • Parameters & conditions
  • Rate limits
  • PII / PCI / PHI handling
{ }
STRUCTURED DATA

Fields. Records. JSON.

action refund.create
amount 640
recipient customer@company.com
customer_name Alex Morgan

Evaluate the action, request attributes and data against your rules.

Aa
UNSTRUCTURED DATA

Messages. Documents. Text.

“Refund $640 to customer@company.com for Alex Morgan.”

Apply those policies when the information arrives as free text.

Policy coverage goes beyond redaction.Control access, actions and sensitive information across both formats.
Illustrative inputs · Enforcement follows your configured policies and access paths.
DETERMINISTIC AT RUNTIME

The rule makes
the decision.

AI can help draft a policy. The model does not decide whether a tool call is allowed. Activated rules are evaluated by the gateway, outside the agent’s prompt.

01

Explicit outcomes

Deny takes precedence over hold, then allow. If no rule matches, the configured fallback applies.

02

Bound to the right access

Effective permissions intersect the agent’s scopes with the person’s access.

03

Update without a redeploy

Activate a reviewed policy version. Subsequent calls use the updated rules.

PRECISE CONTROL. PRACTICAL START.

Bring a policy.
See how it becomes a boundary.

Talk to our team