Low Risk

unfinished_threads

Find conversations worth revisiting: exploring/crystallizing stage with open questions.

How to control unfinished_threads ↓

What unfinished_threads does on Brain

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

Low Risk

Why unfinished_threads needs a policy

This tool searches and retrieves metadata about conversation threads in a 'exploring/crystallizing stage with open questions' state. It has no side effects—it only reads and indexes existing conversation history into searchable results, similar to the sibling tool 'bob_search'.

From the tool's definition Tool name 'unfinished_threads' and description 'Find conversations worth revisiting' indicates a search/query operation that retrieves conversation data. No modification, deletion, execution, or financial operations are performed.

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

How to control unfinished_threads

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

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

unfinished_threads 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 Brain — 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 unfinished_threads

What does the unfinished_threads tool do? +

Find conversations worth revisiting: exploring/crystallizing stage with open questions. It is categorised as a Read tool in the Brain MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on unfinished_threads? +

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

What risk level is unfinished_threads? +

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

Can I rate-limit unfinished_threads? +

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

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

unfinished_threads is provided by the Brain MCP server (mordechaipotash/brain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Brain tool call.

Start from Brain, 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.

34 Brain 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.