MCP governance
Discover server capabilities, review changes, and apply policy to each tool invocation.
Solutions / Govern MCP tools
Your model and tool traffic. One governed boundary.
Point MCP-compatible agents at Aethis to govern calls to your existing MCP servers, and route OpenAI model calls through the same boundary. Reuse credentials, govern tool access, and keep the decisions behind every call in view.
Join the waitlist
Between your agent and its tools.
Every call is checked on the way through.
Point your MCP-compatible agent at an Aethis MCP server URL on mcp.aethis.io. Aethis governs each call and forwards it to your existing MCP server.
Diagram: calls travel from the Agent through Aethis to the MCP server and the system behind it. At Aethis each call is allowed, held until a person approves it, or blocked.
- Allowed Passes straight through.
- Held Waits until a person approves.
- Blocked Stops at Aethis.
MCP client config
"finance": {
-"url": "https://finance.internal/mcp",
+"url": "https://mcp.aethis.io/v1/agents/{agent_id}/mcp",
"headers": {
"Authorization": "Bearer <aethis_agent_token>"
}
}
Tool changes
A tool changed. Nothing runs until you look.
When a server's tools change, Aethis pauses that connection until someone reviews the change.
Illustrative Aethis console with demo data. The Connections page lists MCP connections with their server, the agents and tools that use them, and their status. One connection is picked out: Finance MCP needs its changes reviewed. One tool, finance.refund.create, changed, and tool execution is frozen until the change is reviewed.
A decision for every tool
Most tools just run. You choose the ones that wait.
See every tool an agent can reach, grouped by connection. Policy decides each one: allow it, hold it for a person, or block it.
Illustrative Aethis console with demo data. The Tools table for one agent, Billing Agent, filtered to the tools that need approval or are blocked. On Finance MCP, Issue refund, Capture payment and Create transfer require approval, the refund only when the amount is above SGD 1,000. On Data Operations MCP, Drop database schema is blocked.
One governed proxy
Route OpenAI chat calls through one endpoint, with a spend limit checked before each call.
A vault for your connections
Keep reusable connection credentials in the workspace that owns them. Assign reach to the agents that need it.
Evidence at the boundary
Keep the tool call, policy decision, and execution state connected in an Action Record.
Performance at the boundary
Control should keep up.
Measure gateway overhead, sustained throughput, and the cost of governance together.
Added latencyp95 · milliseconds
Sustained throughputrequests / second
| Capabilities | Aethis | LiteLLM | Gateway X | Gateway Y |
|---|---|---|---|---|
| Model routing & budgets | Result redacted | Result redacted | Result redacted | Result redacted |
| MCP capability discovery | Result redacted | Result redacted | Result redacted | Result redacted |
| Tool-level policy | Result redacted | Result redacted | Result redacted | Result redacted |
| Human approval gates | Result redacted | Result redacted | Result redacted | Result redacted |
| Reusable workspace vaults | Result redacted | Result redacted | Result redacted | Result redacted |
| Capability drift review | Result redacted | Result redacted | Result redacted | Result redacted |
| Action Records | Result redacted | Result redacted | Result redacted | Result redacted |
| Organization & workspace scope | Result redacted | Result redacted | Result redacted | Result redacted |
Go deeperExplore the documentation
Grow your toolset. Keep trust intentional.
Bring an MCP workflow into a governed connection.