Low Risk

get_prompt

Render a named prompt from the target MCP server and return the messages.

How to control get_prompt ↓

What get_prompt does on Kondukt

AI agents call get_prompt to retrieve information from Kondukt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_prompt needs a policy

This tool retrieves and returns prompt content from a target MCP server. It is a read-only operation that fetches existing data without creating, modifying, deleting, executing code, or moving money. The function is analogous to a GET request or query operation. Severity is low because retrieving prompts poses minimal risk to system integrity or security, even if misused by an AI agent.

From the tool's definition Tool description states 'Render a named prompt from the target MCP server and return the messages.' The verb 'Render' and 'return' indicate data retrieval with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_prompt gives an agent:

How to control get_prompt

PolicyLayer is an MCP gateway — it sits between your AI agents and Kondukt, and nothing reaches the server without passing your rules. This is the rule we recommend for get_prompt:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_prompt": {}
  }
}

get_prompt is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Kondukt — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_prompt

What does the get_prompt tool do? +

Render a named prompt from the target MCP server and return the messages. It is categorised as a Read tool in the Kondukt MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_prompt? +

Register the Kondukt MCP server in PolicyLayer and add a rule for 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 Kondukt. Nothing to install.

What risk level is get_prompt? +

get_prompt is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_prompt? +

Yes. Add a rate_limit block to the 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.

How do I block get_prompt completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides get_prompt? +

get_prompt is provided by the Kondukt MCP server (kondukt-dev/core). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kondukt tool call.

Start from Kondukt, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

6 Kondukt tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.