dwaar use cases By agent

Coding agents

Ship faster without giving coding agents a blank cheque.

Coding agents read repositories, modify files, run shell commands, call MCP servers, and interact with deployment systems. dwaar keeps that autonomy aligned with the developer's actual request.

By agent Coding agents Selected use case
dForge
Test before launch

Tests indirect prompt injection, poisoned repository content, unsafe code execution, secret exposure, tool misuse, and unintended file changes.

dFence
Enforce at runtime

Restricts commands, repositories, environments, tools, and MCP calls to the developer's declared task.

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

Test the failure paths. Enforce the intended path.

Coding agents read repositories, modify files, run shell commands, call MCP servers, and interact with deployment systems. dwaar keeps that autonomy aligned with the developer's actual request.

dForge / Before deployment

Find how the workflow can be manipulated.

Tests indirect prompt injection, poisoned repository content, unsafe code execution, secret exposure, tool misuse, and unintended file changes.

dFence / At runtime

Keep live actions aligned with intent.

Restricts commands, repositories, environments, tools, and MCP calls to the developer's declared task.

Example

A security decision in context.

A developer asks the agent to fix a failing checkout test. A poisoned issue instructs it to upload the .env file through an external MCP server. dForge discovers the attack path before launch. dFence identifies that the export does not match "fix the test," blocks the call, and records the event.

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.