FOR CTOs

Build capable AI into a controlled environment.

Give your organization an enforceable control point between agents and business tools. Evaluate integration, deployment and operational behavior before expanding access.

Start your trial →
ARCHITECTURE & DELIVERY

CTO

Assess integration, deployment and the limits that matter before adopting a new control point.

Questions for other teams →
01Where does The Agent Control fit in our architecture?

Place the customer-operated Node between agents and their MCP tools. The Node authenticates clients, validates calls, checks policy and authorized tool definitions, and dispatches permitted actions. The optional remote review service provides review; the customer portal handles account services separately.

02Which clients and protocols are supported?

The current Node supports MCP tools over stdio and Streamable HTTP. Clients must support the required authentication and, when applicable, asynchronous approval handling. Verify each integration: advanced MCP capabilities and delegated OAuth are not universally supported.

03How do we prevent agents from bypassing it?

Route tool connections through the Node and restrict direct access to upstream tools using network controls, process isolation and credential ownership. The Node cannot enforce policy on a call it never sees. Review alternative execution paths as part of deployment.

04Does adding a tool require custom integration code?

Compatible MCP servers can be configured as upstreams, and their tool definitions are discovered for operator review. Tools outside the supported protocol or clients without the required authentication may need adapters. Validate schemas and transport behavior before enabling them.

05What is enforced locally and what needs remote review?

Local checks cover authenticated client identity, tool permission, definition authorization and any required human approval. Configured remote-review rules send selected context to the Center for evaluation. Local permission checks remain necessary regardless of a remote decision.

06What does our team need to operate?

The persistent installation needs the Node runtime, operator console, PostgreSQL, upstream connections and secure configuration. Your team owns TLS, access restrictions, secrets, backups, monitoring and recovery. The installation guide describes local evaluation; production acceptance needs a separate operating review.

07Can we scale it as a highly available cluster?

The current persistent runtime uses a single-runtime database lock; a multi-worker high-availability cluster is not implemented or qualified. Size and benchmark the intended workload, and treat availability requirements as a pilot acceptance criterion rather than assuming horizontal scaling.

08What latency will it add?

Every governed call adds authentication, policy and catalog checks; remote review adds network and evaluation time, and human approval adds operator wait time. There is no published latency SLA. Benchmark representative workloads and distinguish automated checks from approval wait time.

09What execution guarantees can we rely on?

Approval continuation reuses the stored action and prevents concurrent continuations from creating another dispatch. Uncertain outcomes are retained without automatic resend. The final local check and an external effect are not one transaction, so external exactly-once execution is not guaranteed.

10How should we qualify a rollout?

Test real clients and tools, denied calls, changed definitions, approval resumption, review outages and backup restoration. Establish throughput and recovery targets. Accept the pilot against those results before deploying broader or more consequential workloads.

Test controls around a real business workflow.

Start with a 30-day trial, unlimited local operations and 1,000 credits for standard remote evaluations.

Start your trial →Installation guide →