01
For agent builders
Give each agent a smaller, deliberate tool surface instead of a sprawling server list.
Agent tool infrastructure
Agents need tools.
They don't need all of them.
ToolHost is the control plane between an agent and the MCP tools it can reach. Connect the services your team uses, then give each agent the smallest useful capability set.
MCP-nativeTool-level controlOperator evidence
ILLUSTRATIVE TOOL SURFACEPOLICY APPLIED
A
CALLING AGENT
Research assistant
TH
TOOLHOST GATEWAY
A deliberate handoff
identity · policy · evidence
MCP server
Knowledge
search_docs
read_page
cite_source
MCP server
Revenue
find_account
create_quote
issue_refund
MCP server
Engineering
read_repo
run_deploy
rotate_key
3 servers · 9 available tools · 4 exposed to this agent
The governed flight path
Watch the boundary make a decision.
The visual sequence is the product story: an agent asks, the configured view limits discovery, policy evaluates the request, an enabled backend receives it, and the resulting decision is retained.
01
Terminal agent
Requests a toolintent02
Client view
Exposes the allowed surfacediscover03
Policy
Evaluates the calldecide04
MCP backend
Receives the approved callexecute05
Evidence
Retains the decision recordrecordTerminal-native agent work
The agent can live in a terminal. The boundary still holds.
Serious agent work often starts at a shell. ToolHost gives a configured MCP-speaking terminal agent one governed tool surface, while the view, policy, and evidence stay with the team operating the gateway.
One endpointFocused discoveryCall-time policy
Read MCP integration docs ~/work agent tools
connected through ToolHost · view: research
TOOLBACKENDSTATE
search_docsknowledgeexposed
read_pageknowledgeexposed
find_accountrevenueexposed
issue_refundnot in this viewwithheld
~/work _
The problem is not connection
A growing tool list changes how an agent works.
Every MCP server can bring a new set of tools, descriptions, permissions, and operational risk. ToolHost makes the connection useful by making it selective: the agent receives a focused set of tools, while operators retain a single place to manage the boundary.
02
For platform teams
Centralize the point where agent identity, tool policy, and connector access meet.
03
For operators
Manage which configured backends and tools are exposed, then review the resulting decisions and activity.
A policy surface, not another tool catalog
Choose what reaches the agent.
The gateway gives operators a practical place to control what is callable. Start with connected MCP servers; expose only the tools appropriate for a configured client or workflow.
Explore the enterprise modelIllustrative client view
Research assistant
A view controls what this agent can discover. Policy evaluates each request when it is made.
01search_docsknowledge
02read_pageknowledge
03find_accountrevenue
04read_repoengineering
—issue_refundrevenue
How the boundary works
One controlled path from intent to tool call.
01
Prepare
Discover, approve, and enable configured MCP backends before exposing them.
02
Curate
Filter the tools this agent needs. Keep the rest out of its visible surface.
03
Govern
Apply identity, policy, and destination controls at one boundary.
04
Observe
Review decisions and activity at the Gateway boundary.
Start with a smaller surface
Make every agent-tool connection intentional.
ToolHost keeps the agent's tool surface focused while giving your team a governed point of control.