View version history of pmpt snapshots.
AI agents call pmpt_history to retrieve information from Pmpt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays version history records—a passive query operation with no capability to modify, delete, or execute changes. It fits the Read category: retrieves or queries data with no side effects. The low severity reflects minimal blast radius if an AI agent misuses it, as viewing history cannot harm data or systems.
From the tool's definition Tool name 'pmpt_history' and description 'View version history of pmpt snapshots' indicate a read-only operation that retrieves historical data without modification or side effects.
Documented attack patterns abuse exactly the kind of access pmpt_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pmpt, and nothing reaches the server without passing your rules. This is the rule we recommend for pmpt_history:
{
"version": "1",
"default": "deny",
"tools": {
"pmpt_history": {}
}
}pmpt_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
View version history of pmpt snapshots. It is categorised as a Read tool in the Pmpt MCP Server, which means it retrieves data without modifying state.
Register the Pmpt MCP server in PolicyLayer and add a rule for pmpt_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 Pmpt. Nothing to install.
pmpt_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 pmpt_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 pmpt_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.
pmpt_history is provided by the Pmpt MCP server (pmptwiki/pmpt-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pmpt, 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.
14 Pmpt tools catalogued and risk-classified — across an index of 43,000+ MCP servers.