Retrieve a rendered prompt with arguments from the connected MCP server.
AI agents call inspector_get_prompt to retrieve information from Mcp Inspector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_id | string | Yes | Session ID returned by inspector_connect |
prompt_args | object | — | String key-value arguments for the prompt template |
prompt_name | string | Yes | Name of the prompt to retrieve |
Parameters from the server's own tool schema.
This tool fetches prompt data from a connected MCP server. It has no side effects, does not execute code, does not modify state, and does not delete or move resources. It is purely a data retrieval operation, making it a Read risk category with low severity—misuse would only expose existing prompts, not cause operational damage.
From the tool's definition Tool description states 'Retrieve a rendered prompt' — retrieves data without modification. The verb 'Retrieve' and lack of any mutation language (create, update, delete, execute) confirm read-only semantics.
Attacks that exploit this kind of access
Retrieve a rendered prompt with arguments from the connected MCP server. It is categorised as a Read tool in the Mcp Inspector MCP Server, which means it retrieves data without modifying state.
inspector_get_prompt accepts 3 parameters: session_id, prompt_args, prompt_name. Required: session_id, prompt_name. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Inspector MCP server in PolicyLayer and add a rule for inspector_get_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 Mcp Inspector. Nothing to install.
inspector_get_prompt 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 inspector_get_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 inspector_get_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.
inspector_get_prompt is provided by the Mcp Inspector MCP server (@fre4x/mcp-inspector). 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 →