LangChain launches Tool Gateway in public beta to manage agents’ tool credentials
On 19 November LangChain added Tool Gateway to its LangSmith platform. The service attaches stored credentials and policies to an agent’s tool calls, so developers do not have to write credentials into the agent’s code.
Tool Gateway is a managed layer from LangChain that sits between an agent and MCP servers. An MCP server gives the agent tools from an external service such as Linear or Notion. According to LangChain’s documentation, the agent authenticates only to LangSmith. Tool Gateway then picks a stored credential and uses it to authenticate to the server. The agent therefore never holds the service’s key.
A call runs either with the user’s own credentials or on the agent’s behalf. A call on the agent’s behalf uses the agent’s own credentials or a profile: shared credentials that an administrator has connected once. LangChain’s blog gives the example of a large US retailer with more than 50 MCP servers and more than a thousand tools. The retailer is building a store assistant that acts with each employee’s credentials, and an agent that reconciles inventory overnight with its own service credentials.
A tool kit gathers selected tools under a single MCP URL. The documentation stresses that a kit does not restrict access: the same caller can use kits/me/mcp, which serves every tool that caller is allowed to use. Policies restrict use instead. A deny policy blocks a call, and an approval policy asks the MCP client’s user to confirm it. A separate reviewer cannot approve calls, and tools are allowed by default. Customers can enable deny policies and the audit log by contacting the LangChain team, the blog said. The log is part of the Enterprise plan.
When tracing is switched on, it records metadata for each call, such as the tool, server and identity, but not the data sent or returned. Tool Gateway passes the server’s response through unchanged, so the agent must treat it as untrusted input, the documentation says.
Tool Gateway, which is in beta, is available on LangSmith’s Plus and Enterprise plans in the GCP US, EU and APAC regions and the AWS US region, but not in the Azure US region. The quickstart has users try the tools from, for example, Claude Code with a personal access token. It advises using a test workspace, because a tool in the example kit can create issues in Linear.
Read more: How an agent works · Agent map