dwaar use cases By agent

Customer support agents

Resolve customer issues without exposing customer data.

Support agents search knowledge bases, read account history, update tickets, issue refunds, and communicate directly with customers. One manipulated message can turn legitimate access into data leakage or fraud.

By agent Customer support agents Selected use case
dForge
Test before launch

Tests prompt injection in tickets, attachments, and retrieved content, along with cross-customer leakage, policy hallucination, and refund abuse.

dFence
Enforce at runtime

Scopes CRM, order, and refund tools to the customer's request and escalates sensitive actions.

Intent + context One security model across the agent lifecycle
Customer support agents in practice

Test the failure paths. Enforce the intended path.

Support agents search knowledge bases, read account history, update tickets, issue refunds, and communicate directly with customers. One manipulated message can turn legitimate access into data leakage or fraud.

dForge / Before deployment

Find how the workflow can be manipulated.

Tests prompt injection in tickets, attachments, and retrieved content, along with cross-customer leakage, policy hallucination, and refund abuse.

dFence / At runtime

Keep live actions aligned with intent.

Scopes CRM, order, and refund tools to the customer's request and escalates sensitive actions.

Example

A security decision in context.

A customer asks why an order is delayed. An attached document instructs the agent to export all customer records. dFence allows the order lookup but blocks the unrelated export because its intent falls outside the support workflow.

One security model

The use case changes. The security loop stays the same.

For every agent, dwaar asks four questions: What is the agent supposed to do? Which data and tools should it reach? How could that workflow be manipulated? What should happen when its behavior drifts?

01

Define

Document the happy path, permitted tools, data boundaries, and approval points.

02

Test

dForge attacks the workflow before launch using context-specific prompt, tool-use, and multi-turn tests.

03

Enforce

dFence evaluates runtime intent before sensitive tool and MCP calls, then allows, blocks, constrains, redacts, or requests approval.

04

Improve

Turn verified findings and runtime events into stronger policies and repeatable security tests.

Build with control

Know where your agent can be misused before it goes live.

dwaar combines agent-specific adversarial testing with intent-aware runtime enforcement, helping teams deploy capable agents without relying on static scopes alone.