Skip to content

AgentBoundary

Get the workflow to hold still before you test it.

A test result means very little if the prompts, tools or permissions changed halfway through the run. Before an AgentBoundary assessment, we review the proposed configuration, the approval controls and the logging, and tell you what has to change first.

Included in the work

What has to be pinned down before testing.

  • Assessment scope review
  • Prompt, model, memory, and tool-change risk notes
  • Approval-gate and logging review
  • Excessive-agency risk checklist
  • Remediation plan before formal testing

01

Readiness questions

  • Are the prompts, model, memory behavior and tool scopes stable enough to test?
  • Can the team approve or deny a high-impact action, record the outcome and stop further work? Which effects can be undone?
  • Can you reconstruct tool calls and retrieval paths from the logs?
  • Would a model swap, a prompt change or a new MCP server invalidate the assumptions you're about to test?

02

Readiness output

Likely blockers

The missing controls and unstable configurations that would make the planned result unreliable.

Stability checklist

The prompts, model configuration, memory behavior, tool permissions and approval rules the test will use, written down, plus a log of anything that changes during the assessment.

Recommended path

Go to formal testing, widen to a broader assessment, or fix some things first.

03

The benchmark is not the application test

The open AgentBoundary benchmark sends 51 prompt-injection scenarios through chat-completion APIs and looks at how the model responds. It doesn't execute tools in a live application. If a commercial assessment also checks application permissions or downstream actions, those are separate tests and the report has to say so.

Limits

Scope and limitations.

  • A readiness review doesn't issue a certification or a passing result.
  • No AgentBoundary certifications have been issued or published. Badge criteria have to be published before any certification can exist, and being ready for assessment doesn't establish eligibility.

Next step

Bring the workflow you plan to test.

Request readiness review