Manage Agents

Before Vijil can evaluate or protect an Agent, you need to register it. Registration tells Vijil how to communicate with your Agent and how much visibility you are granting for analysis. You can register and manage Agents two ways: through the Console web interface, or through MCP by describing what you want in plain English to Claude Code. Use the tabs in each section to follow the path you prefer.

Access Levels

Vijil supports three access levels, each enabling progressively deeper evaluation. The access level you choose determines what Vijil can analyze and what vulnerabilities it can detect.

Access Level	What You Provide	What Vijil Can Test
Black Box	API endpoint and credentials	Input/output behavior only
Grey Box	Model config, MCP config, A2A config	Vulnerabilities traced to the Agent’s composition
White Box	Full configuration and source code	SAST and DAST analysis for thorough audit

Black Box

Black Box registration requires minimal information: your Agent’s API endpoint and authentication. Vijil treats the Agent as an opaque system, testing only its observable behavior. This approach works well for:

Third-party Agents you do not control
Initial evaluations before deeper analysis
Agents where you want to test the API contract

Black Box fields:

Agent Name: A descriptive identifier
Agent URL: Remote Agent endpoint URL
Use A2A Protocol: Enable Agent to Agent protocol
Optional Purpose: Description of what the Agent is for
Access Key: Authentication credentials (you can add multiple keys)
Rate Limit Per Minute: Matches your provider’s limits to avoid throttling

Grey Box

Grey Box expands visibility into your Agent’s composition. This enables Vijil to trace vulnerabilities to specific components whether a prompt injection succeeded because of the model choice, MCP tool exposure, or delegated Agent behavior. Grey Box settings:

Section	Fields	Purpose
Role & Instructions	Role, System Prompt	Helps Vijil understand expected behavior
Capabilities	Capability tools	Add one or more Capability tools
Model Configuration	Model name, Temperature, Max tokens, Top P	Defines the model and generation settings used during evaluation
External Resources	MCP Proxy or Server, MCP Access Level	Tests tool-use attack surfaces
Delegated Agents	A2A Card URLs	Evaluates orchestration risks for delegated Agents

If your Agent uses MCP tools or delegates to sub-agents, Grey Box registration enables Vijil to test the full execution graph—not just the top-level API.

White Box

White Box provides full source code access for static analysis (SAST) combined with dynamic testing (DAST). This is the most thorough evaluation path. White Box fields:

Source Code: Paste code directly, or leave empty to pull from repository
GitHub Repository: Repository URL, Entry point, Username, and Access token for private repos

White Box evaluation can identify vulnerabilities that Black Box testing would miss—hardcoded secrets, unsafe deserialization, SQL injection in tool implementations, and similar code-level issues.

Register an Agent

Console
MCP

The Agent Registry

Navigate to Agents in the sidebar to open the Agent Registry. The registry displays all Agents in your workspace with key information:

Column	What It Shows
Name	Identifier you assigned during registration
Owner	Team member who registered the Agent
Registered	Date and time when the Agent was registered
Stage	Current lifecycle stage: Registered, Tested, Protected, or Adapted
Time in Stage	How long the Agent has been in its current stage
Trust Score	Current score from most recent evaluation

Registering an Agent

Navigate to Agents in the sidebar to open the Agent Registry
Click + Register Agent to open the Register Agent form
Fill in the Black Box fields (required for all Agents)
Expand Grey Box if you want compositional analysis
Expand White Box if you want source code analysis
Click Register Agent

Connect Claude Code to your Vijil account once, then register Agents by describing them in plain English.

One-time setup: connect Claude Code to Vijil

Install the Vijil tools. vijil-mcp connects Claude Code to Vijil and pulls in the vijil command-line tool as a dependency:

pipx install vijil-mcp

If you do not have pipx, use pip install vijil-mcp (or pip3). Confirm both tools are available:

vijil --help
vijil-mcp --help

Point the tool at your Console and log in with the same email and password you use for the Console website:

vijil auth init --url https://console-api.your-company.com
vijil auth login

If you belong to more than one team, choose which to use:

vijil team list
vijil team use <team_id>

Finally, create a .mcp.json file in your working folder so Claude Code launches the Vijil tools:

{
  "mcpServers": {
    "vijil": {
      "type": "stdio",
      "command": "vijil-mcp"
    }
  }
}

Start Claude Code in that folder and type “Check my Vijil setup” to confirm everything is connected. For access in every folder, add the same block to ~/.claude.json instead.

Tell Claude about the AI Agent you want to register. Provide its name, the model it uses, and its API endpoint and key:

Create a new agent called 'My Chat Agent' using gpt-4o at https://api.openai.com/v1/chat/completions with API key sk-...

Claude registers the Agent and shows you its ID. Keep that ID handy, you will use it when running evaluations.

Manage Agents

Console
MCP

Click the Actions menu (three dots) on any Agent row to access management options.

Action	What It Does
View	View Agent configuration
Edit	Update Agent configuration
Clone	Create a copy with a new name
Export JSON	Download configuration for backup or migration
Delete	Permanently remove an Agent and all associated data

Editing an Agent

Select Edit to open the Agent configuration form with current values populated. Make your changes and click Save Changes.

Changing an Agent’s configuration may affect ongoing evaluations. If you need to test different configurations, consider using Clone to create a variant instead.

Agent Stage

Agents progress through lifecycle stages:

Stage	Meaning
Registered	The Agent has been registered in the platform
Tested	At least one evaluation has been run against the Agent
Protected	Dome has been configured and enabled for the Agent
Adapted	At least one Darwin proposal has been accepted for the Agent following an evolution run

Use Stage to understand where an Agent is in the evaluation, protection, and adaptation lifecycle.

Get Started

Teams

Agents

Build an Evaluation Environment

Evaluate Agents

Protect Agents

Manage Agents

Access Levels

Black Box

Grey Box

White Box

Register an Agent

The Agent Registry

Registering an Agent

Manage Agents

Editing an Agent

Agent Stage

Next Steps

Define Personas

Define Policies

​Access Levels

​Black Box

​Grey Box

​White Box

​Register an Agent

​The Agent Registry

​Registering an Agent

​Manage Agents

​Editing an Agent

​Agent Stage

​Next Steps

Define Personas

Define Policies

Access Levels

Black Box

Grey Box

White Box

Register an Agent

The Agent Registry

Registering an Agent

Manage Agents

Editing an Agent

Agent Stage

Next Steps