Low Risk

search_conversations

Full-text search across all Claude Code conversations. Find where you discussed specific topics.

How to control search_conversations ↓

What search_conversations does on Claude Code Toolkit

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

Low Risk

Why search_conversations needs a policy

This tool retrieves and queries conversation data without creating, modifying, deleting, or executing anything. It is a passive information retrieval operation with no side effects, fitting the Read category.

From the tool's definition Tool performs 'full-text search across all Claude Code conversations' with no indication of modification, deletion, or execution capabilities. The verb 'search' and 'find' indicate retrieval operations only.

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

How to control search_conversations

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

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

search_conversations 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 Claude Code Toolkit — 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 search_conversations

What does the search_conversations tool do? +

Full-text search across all Claude Code conversations. Find where you discussed specific topics. It is categorised as a Read tool in the Claude Code Toolkit MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_conversations? +

Register the Claude Code Toolkit MCP server in PolicyLayer and add a rule for search_conversations: 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 Toolkit. Nothing to install.

What risk level is search_conversations? +

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

Can I rate-limit search_conversations? +

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

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

search_conversations is provided by the Claude Code Toolkit MCP server (asifkibria/claude-code-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Code Toolkit tool call.

Start from Claude Code Toolkit, 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.

40 Claude Code Toolkit 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.