Discover recurring patterns in conversation history: common topics, frequent workflows, repeated issues.
AI agents call find_patterns to retrieve information from ClaudeHistoryMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
find_patterns retrieves and analyzes conversation history to identify patterns. It has no side effects, does not modify or delete data, does not execute code or commands, and does not involve financial transactions. The operation is purely informational — extracting insights from existing data. This is classic Read category behavior.
From the tool's definition Tool performs discovery and analysis operations: "Discover recurring patterns", "common topics", "frequent workflows", "repeated issues" — all read-only aggregation and analysis of historical data without modification or deletion.
Documented attack patterns abuse exactly the kind of access find_patterns gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ClaudeHistoryMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for find_patterns:
{
"version": "1",
"default": "deny",
"tools": {
"find_patterns": {}
}
} find_patterns 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.
Discover recurring patterns in conversation history: common topics, frequent workflows, repeated issues. It is categorised as a Read tool in the ClaudeHistoryMCP MCP Server, which means it retrieves data without modifying state.
Register the ClaudeHistory MCP server in PolicyLayer and add a rule for find_patterns: 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 ClaudeHistoryMCP. Nothing to install.
find_patterns 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 find_patterns 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 find_patterns. 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.
find_patterns is provided by the ClaudeHistory MCP server (jhammant/claudehistorymcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ClaudeHistoryMCP, 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.
9 ClaudeHistoryMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.