AI agents call get_prompt_by_name 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 |
|---|---|---|---|
prompt_name | string | Yes | The exact name of the prompt to retrieve |
Parameters from the server's own tool schema.
This tool retrieves prompt configuration data by name. It has no side effects—it only queries and returns existing data. No data is created, modified, deleted, or executed. The operation is read-only, placing it clearly in the Read category with low severity.
From the tool's definition Tool name is 'get_prompt_by_name' and description states it 'Get[s] a specific prompt by its exact name' with a return of 'prompt details and template'. This is a retrieval operation with no mention of modification, deletion, or code execution.
Attacks that exploit this kind of access
Get a specific prompt by its exact name. Args: prompt_name (str): The exact name of the prompt to retrieve Returns: Dict containing the prompt details and template, or an error message. It is categorised as a Read tool in the Langsmith MCP Server, which means it retrieves data without modifying state.
get_prompt_by_name accepts 1 parameter: prompt_name. Required: prompt_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 get_prompt_by_name: 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_prompt_by_name 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_prompt_by_name 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_prompt_by_name. 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_prompt_by_name 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.
get_prompt_by_name is one line of Langsmith's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →