prompts_prompt_history
List past versions of a prompt template's prompt_text. Every edit is snapshotted to an append-only table — use this to browse history and find a version_number for prompts.prompt_restore.
This record as markdown: /tools/io-github-saloprj-dialogbrain/prompts-prompt-history.md
What prompts_prompt_history does on Dialogbrain
AI agents call prompts_prompt_history to retrieve information from Dialogbrain without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max versions to return (1-200, default 50) |
prompt_id | integer | Yes | ID of the prompt template |
before_version | integer | — | Cursor: return versions strictly below this version_number |
Parameters from the server's own tool schema.
Why prompts_prompt_history is rated Low
The tool only reads historical snapshots from an append-only table. It performs no writes, executions, or deletions. The severity is low because misuse only exposes prompt history data.
From the tool's definition 'List past versions of a prompt template's prompt_text' and 'browse history' — purely retrieval from an append-only table with no side effects
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs prompts_prompt_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For prompts_prompt_history, this is the rule to start with:
prompts_prompt_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every prompts_prompt_history call is checked against it from then on.
Questions about prompts_prompt_history
List past versions of a prompt template's prompt_text. Every edit is snapshotted to an append-only table — use this to browse history and find a version_number for prompts.prompt_restore. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
prompts_prompt_history accepts 3 parameters: limit, prompt_id, before_version. Required: prompt_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for prompts_prompt_history: 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 Dialogbrain. Nothing to install.
prompts_prompt_history 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 prompts_prompt_history 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 prompts_prompt_history. 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.
prompts_prompt_history is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue