List LangSmith projects with optional filtering and detail level control. Args: limit (int): Maximum number of projects to return (default: 5) project_name (str, optional): Filter projects by name (partial match) more_info (str): "true" for full details, "false" for simplified (default: "false") ...
AI agents call list_projects 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 |
|---|---|---|---|
limit | number | — | Maximum number of projects to return |
more_info | string | — | "true" for full details, "false" for simplified |
project_name | string | — | Filter projects by name using partial matching |
reference_dataset_id | string | — | Filter by reference dataset ID |
reference_dataset_name | string | — | Filter by reference dataset name |
Parameters from the server's own tool schema.
This is a straightforward data retrieval tool that queries and lists existing projects with optional filtering. It has no side effects, does not modify state, and cannot execute code or access financial systems. The worst-case misuse would be information disclosure of project metadata, which is low severity.
From the tool's definition Tool name is 'list_projects' and description states it 'List[s] LangSmith projects with optional filtering and detail level control.' The arguments are all read-only filters (limit, project_name, more_info, reference_dataset_id, reference_dataset_name) with…
Attacks that exploit this kind of access
List LangSmith projects with optional filtering and detail level control. Args: limit (int): Maximum number of projects to return (default: 5) project_name (str, optional): Filter projects by name (partial match) more_info (str): "true" for full details, "false" for simplified (default: "false") reference_dataset_id (str, optional): Filter by reference dataset ID reference_dataset_name (str, optional): Filter by reference dataset name. It is categorised as a Read tool in the Langsmith MCP Server, which means it retrieves data without modifying state.
list_projects accepts 5 parameters: limit, more_info, project_name, reference_dataset_id, reference_dataset_name. 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 list_projects: 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.
list_projects 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 list_projects 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 list_projects. 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.
list_projects 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 →