Call this tool when you need to understand how to create and push prompts to LangSmith. This is a documentation-only tool that explains how to: - Create prompts using LangChain's prompt templates - Push prompts to LangSmith for version control and management - Handle prompt creation vs. version u...
AI agents use push_prompt to create or update resources in Langsmith — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Langsmith environment.
This tool creates and modifies prompts in LangSmith, which is a reversible operation (prompts can be updated or reverted via version control). It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or retrieve-only operations (Read).
From the tool's definition Tool description explicitly states it "Call this tool when you need to understand how to create and push prompts to LangSmith" and mentions "Push prompts to LangSmith for version control and management" and "Handle prompt creation vs. version updates".
Attacks that exploit this kind of access
Call this tool when you need to understand how to create and push prompts to LangSmith. This is a documentation-only tool that explains how to: - Create prompts using LangChain's prompt templates - Push prompts to LangSmith for version control and management - Handle prompt creation vs. version updates Use the LangSmith Client's push_prompt() method. See LangSmith documentation for details. It is categorised as a Write tool in the Langsmith MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Langsmith MCP server in PolicyLayer and add a rule for push_prompt: 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.
push_prompt is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the push_prompt 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 push_prompt. 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.
push_prompt 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 →