AI agents call update_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.
The tool explicitly states it is 'documentation-only', meaning it only retrieves/displays information about how to update dataset examples rather than actually performing any updates. No data modification occurs.
From the tool's definition This is a documentation-only tool
Attacks that exploit this kind of access
Call this tool when you need to understand how to update dataset examples in LangSmith. This is a documentation-only tool. It is categorised as a Read tool in the Langsmith MCP Server, which means it retrieves data without modifying state.
Register the Langsmith MCP server in PolicyLayer and add a rule for update_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.
update_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 update_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 update_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.
update_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 →