Fetch organization billing usage (trace counts) with workspace names inline. Args: starting_on (str): Start of date range (ISO 8601) ending_before (str): End of date range (ISO 8601) workspace (str, optional): Optional workspace UUID or display name to filter on_current_plan (str): "true" to incl...
AI agents call get_billing_usage to retrieve information from Langsmith without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
workspace | string | — | Optional workspace UUID or display name to filter |
starting_on | string | Yes | Start of date range (ISO 8601) |
ending_before | string | Yes | End of date range (ISO 8601) |
on_current_plan | string | — | "true" to include only usage on current plan |
Parameters from the server's own tool schema.
This is a Read operation that queries billing/usage data. While the data retrieved could be sensitive (billing information, usage metrics), the tool itself performs no side effects, creates no obligations, and makes no changes.
From the tool's definition Tool description states 'Fetch organization billing usage' - a retrieval operation with no modification. Arguments are all query filters (date ranges, workspace filter, plan filter) with no write or destructive capabilities.
Attacks that exploit this kind of access
Fetch organization billing usage (trace counts) with workspace names inline. Args: starting_on (str): Start of date range (ISO 8601) ending_before (str): End of date range (ISO 8601) workspace (str, optional): Optional workspace UUID or display name to filter on_current_plan (str): "true" to include only usage on current plan (default: "true"). It is categorised as a Read tool in the Langsmith MCP Server, which means it retrieves data without modifying state.
get_billing_usage accepts 4 parameters: workspace, starting_on, ending_before, on_current_plan. Required: starting_on, ending_before. The full parameter table on this page comes from the server's own tool schema.
Register the Langsmith 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. 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 (langsmith-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →