Get paginated conversation history (use after exploring with list_projects/list_sessions for targeted data)
AI agents call get_conversation_history to retrieve information from Claude Code History MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical conversation data from local projects without creating, modifying, or deleting any information. Pagination and filtering are query operations that pose minimal risk when misused—an agent might retrieve more data than intended, but cannot alter or destroy it. Classified as Read with low severity due to the absence of side effects or destructive potential.
From the tool's definition Tool description states 'Get paginated conversation history' with no modification or deletion capabilities.
Documented attack patterns abuse exactly the kind of access get_conversation_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code History MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_conversation_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_conversation_history": {}
}
}get_conversation_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.
Get paginated conversation history (use after exploring with list_projects/list_sessions for targeted data). It is categorised as a Read tool in the Claude Code History MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Claude Code History MCP Server MCP server in PolicyLayer and add a rule for get_conversation_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 Claude Code History MCP Server. Nothing to install.
get_conversation_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 get_conversation_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 get_conversation_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.
get_conversation_history is provided by the Claude Code History MCP Server MCP server (yudppp/claude-code-history-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Code History MCP Server, 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.
4 Claude Code History MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.