Fetch examples from a LangSmith dataset with advanced filtering options. Either dataset_id, dataset_name, or example_ids must be provided. Args: dataset_id (str, optional): Dataset ID to retrieve examples from dataset_name (str, optional): Dataset name to retrieve examples from example_ids (str, ...
AI agents call list_examples 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 |
|---|---|---|---|
as_of | string | — | Dataset version tag or ISO timestamp |
limit | number | — | Maximum number of examples to return |
filter | string | — | Filter string using LangSmith query syntax |
offset | string | — | Number of examples to skip |
splits | string | — | Dataset splits as JSON array string or single split |
metadata | string | — | Metadata filter as JSON object string |
dataset_id | string | — | Dataset ID to retrieve examples from |
example_ids | string | — | Example IDs as JSON array string or single ID |
dataset_name | string | — | Dataset name to retrieve examples from |
inline_s3_urls | string | — | "true" or "false" |
include_attachments | string | — | "true" or "false" |
Parameters from the server's own tool schema.
This tool retrieves and queries data from a LangSmith dataset without modifying, deleting, or executing any operations. It is a read-only operation that returns examples based on filter criteria. No side effects or data mutations occur.
From the tool's definition Tool name is 'list_examples' and description states 'Fetch examples from a LangSmith dataset' with filtering options. Arguments are all optional query parameters (dataset_id, dataset_name, example_ids, filter, metadata, splits, inline_s3_urls) for retrieval.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
Fetch examples from a LangSmith dataset with advanced filtering options. Either dataset_id, dataset_name, or example_ids must be provided. Args: dataset_id (str, optional): Dataset ID to retrieve examples from dataset_name (str, optional): Dataset name to retrieve examples from example_ids (str, optional): Example IDs as JSON array string or single ID filter (str, optional): Filter string using LangSmith query syntax metadata (str, optional): Metadata filter as JSON object string splits (str, optional): Dataset splits as JSON array string or single split inline_s3_urls (str, optional): "true" or "false" include_attachments (str, optional): "true" or "false" as_of (str, optional): Dataset version tag or ISO timestamp limit (int): Max examples to return (default: 10) offset (str, optional): Number of examples to skip. It is categorised as a Read tool in the Langsmith MCP Server, which means it retrieves data without modifying state.
list_examples accepts 11 parameters: as_of, limit, filter, offset, splits, metadata, dataset_id, example_ids, dataset_name, inline_s3_urls, include_attachments. 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_examples: 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_examples 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_examples 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_examples. 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_examples 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 →