THE AGENT CONTROL Customer portal
AGENT ACTION GOVERNANCE

Give every agent action
a clear boundary.

Put explicit policy between AI agents and the tools they can use. Review access, mediate calls, and keep operations in your own environment.

See how it works Explore deployment
⌘Self-hosted gatewayMCP compatibleOperator controlled
SCROLL TO EXPLORE
Clear permissionsHuman review when requiredCustomer controlled infrastructureBuilt for existing MCP tools
THE CONTROL LAYER

More control around
the tools agents already use.

The Agent Control sits between an agent and its connected MCP servers. It makes each tool visible to an operator and applies an explicit access decision before a call is dispatched.

01 / DISCOVER

See the available tools

Bring compatible MCP servers behind one gateway and review the tool catalog before exposing it to an agent.

Explore the flow
02 / GOVERN

Apply explicit policy

Allow only the clients and tools you configure. A denial wins over a matching allow, and unapproved tool definitions stay blocked.

Explore the flow
03 / REVIEW

Keep operators in control

Use the local console to inspect policy, review approval requests, and follow recorded activity for the installation.

Explore deployment
A GOVERNED PATH TO EXECUTION

One clear path from
request to result.

Connect the tools your agents already depend on. Give each client an identity, set the rules, and let the gateway enforce those rules at the boundary.

See deployment model
i

Controls apply to calls routed through The Agent Control. Restrict direct access to upstream tools in your environment too.

DESIGNED FOR YOUR ENVIRONMENT

Your tools. Your policies.
Your operating boundary.

The gateway and operator console run with your workloads. The product portal is a separate service surface for organization access and product support.

01
PRIVATE INSTALLATION

Run the control layer where your work runs.

Keep tool credentials, operational policies, approval decisions, and audit records within infrastructure you manage.

Customer operated
02
OPEN INTEGRATION

Keep your agents and frameworks.

Connect MCP clients through a configured gateway and continue using your existing agent stack.

MCP gateway
03
PRODUCT PORTAL

A separate place for account services.

The customer portal will handle organization access, licensing, releases, and support. It does not control private agent operations.

Visit the portal
BUILT AROUND BOUNDED AUTHORITY

Useful by design.
Limited by policy.

01

Default deny

Access requires an explicit matching rule. Denials take precedence.

02

Review exact tool definitions

New or changed tool definitions need operator authorization before use.

03

Keep authority local

The product portal does not grant agent permissions or administer customer installations.

QUESTIONS, ANSWERED

Frequently asked
questions.

A few details about where The Agent Control fits and how it is operated.

Does this replace my agent framework?

No. The Agent Control is a governance layer for tool access. Your agents, models, and frameworks remain yours.

Where does the operational console run?

The operator console belongs to the private installation and runs with the gateway in infrastructure you manage. It is separate from the customer portal.

Which tools can I connect?

The current gateway supports MCP servers over stdio and Streamable HTTP. Each installation should verify client compatibility and restrict direct access to upstream tools.

Does the portal receive prompts or tool data?

No. Operational prompts, tool inputs, credentials, and audit records stay in the customer managed installation by default. Support diagnostics should be shared explicitly and redacted.

Can I see pricing or create an account today?

Not yet. Licensing and portal onboarding are still being defined. Contact your product representative for current project information.

THE AGENT CONTROL

Put a clear boundary
around every action.

Make agent access visible, reviewable, and governed inside the environment you control.

Explore the product