Specify the action.
Check amounts, recipients, destinations and other request attributes.
Turn plain-language intent into reviewed, deterministic policies for configured tool calls.
See Policy FirewallSet conditions on amounts, recipients and destinations. Limit call volume. Preview decisions in shadow mode before enforcing.
“Hold refunds above $500 for review.”
refund.create$500Hold for reviewrefund.create$640 exceeds the configured $500 boundary.
Check amounts, recipients, destinations and other request attributes.
Set limits on how often agents can use configured tools.
Record the verdict a rule would produce before applying it to live requests.
Detect personal, payment and health information. Apply your policy to redact, mask, pseudonymize or drop sensitive values before they reach the agent.
Identify personal details such as names and Social Security numbers.
Recognize payment card data and limit what the agent receives.
Find sensitive health identifiers, including medical record numbers.
Illustrative transformations · Detection and treatment depend on configured policies. Name detection uses optional named-entity recognition.
All the policies you configure apply across structured and unstructured data—including how PII, PCI and PHI are handled.
Your configured policiesaction refund.create
amount 640
recipient customer@company.com
customer_name Alex MorganEvaluate the action, request attributes and data against your rules.
“Refund $640 to customer@company.com for Alex Morgan.”
Apply those policies when the information arrives as free text.
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.
Deny takes precedence over hold, then allow. If no rule matches, the configured fallback applies.
Effective permissions intersect the agent’s scopes with the person’s access.
Activate a reviewed policy version. Subsequent calls use the updated rules.