AI agents call get_billing_usage to retrieve information from LangSmith MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches billing or usage information from the LangSmith platform. It does not write, delete, or execute external operations — it queries existing data. Even though it concerns billing, there is no financial transaction involved (no payments, refunds, or subscription changes initiated). The primary action is retrieval, classifying it as Read.
From the tool's definition Tool name is 'get_billing_usage' — contains 'get' which is a read operation. The 'billing_usage' suffix indicates it retrieves usage/billing data, a query operation. No description provided, but the naming pattern is consistent with data retrieval.
Documented attack patterns abuse exactly the kind of access get_billing_usage gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LangSmith MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_billing_usage:
{
"version": "1",
"default": "deny",
"tools": {
"get_billing_usage": {}
}
}get_billing_usage is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_billing_usage. It is categorised as a Read tool in the LangSmith MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LangSmith MCP Server MCP server in PolicyLayer and add a rule for get_billing_usage: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches LangSmith MCP Server. Nothing to install.
get_billing_usage is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_billing_usage rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_billing_usage. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_billing_usage is provided by the LangSmith MCP Server MCP server (langchain-ai/langsmith-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LangSmith MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 LangSmith MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.