Interceptor Sandbox

Interceptor gives an AI agent a controlled world to operate in. It runs the agent in a container with declared services, files, identities, and data, then records how it interacts with that world.

Simulate the dependencies the agent needs

An agent may depend on HTTP APIs, MCP tools, a database, model providers, and files. The environment blueprint describes those dependencies and how to invoke the agent. Interceptor provides the supported simulated services inside the environment, including managed PostgreSQL/pgvector, so you do not need a separate database server for a supported database-backed target.

Model and embedding computation can use explicitly configured host-side provider connections. Declared HTTPS seams can reach particular external services. These connections are distinct from simulated services and do not provide general network access to the target.

Observe and compare behavior

Interceptor records requests, responses, managed state changes, and target output. Supported snapshots preserve declared logical state so experiments can start from known conditions. They do not automatically capture process memory, open connections, or remote service state.

You can operate Interceptor through its CLI and local API, or connect Operator for campaigns driven by Attack Harness. Interceptor supplies the target environment; the campaign supplies the investigation objectives.

Bring your first agent

Follow setup, bring your agent, and blueprint creation. Use the service reference to model its dependencies and sessions and evidence to inspect it.

The customer-support walkthrough shows these steps together with Operator and Attack Harness.