A detailed tool for dynamic and reflective problem-solving through thoughts. This tool helps analyze problems through a flexible thinking process that can adapt and evolve. Each thought can build on, question, or revise previous insights as understanding deepens. Supports forward thinking (1→N), ...
High parameter count (11 properties)
Part of the Clear Thought 1 5 MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents may call clear_thought to permanently remove or destroy resources in Clear Thought 1 5. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call clear_thought in a loop, permanently destroying resources in Clear Thought 1 5. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
tools:
clear_thought:
rules:
- action: deny
reason: "Blocked by default — enable with approval" See the full Clear Thought 1 5 policy for all 2 tools.
Agents calling destructive-class tools like clear_thought have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.
clear_thought is one of the critical-risk operations in Clear Thought 1 5. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.
A detailed tool for dynamic and reflective problem-solving through thoughts. This tool helps analyze problems through a flexible thinking process that can adapt and evolve. Each thought can build on, question, or revise previous insights as understanding deepens. Supports forward thinking (1→N), backward thinking (N→1), or mixed approaches. When to use this tool: - Breaking down complex problems into steps - Planning and design with room for revision - Analysis that might need course correction - Problems where the full scope might not be clear initially - Problems that require a multi-step solution - Tasks that need to maintain context over multiple steps - Situations where irrelevant information needs to be filtered out Thinking Approaches: **Forward Thinking (Traditional Chain of Thought)**: Start at thought 1, work sequentially to thought N - Use when: Exploring unknowns, brainstorming, open-ended analysis, discovery - Pattern: thoughtNumber 1 → 2 → 3 → ... → N - Example: "How can we improve user engagement?" Start with current state, explore options, reach conclusion **Backward Thinking (Goal-Driven Reasoning)**: Start at thought N (desired end state), work back to thought 1 (starting conditions) - Use when: Designing systems, planning projects, solving well-defined problems, working from goals - Pattern: thoughtNumber N → N-1 → N-2 → ... → 1 - Example: "Design a caching strategy for 10k req/s" Start with success criteria (thought 8), work backwards through prerequisites (monitoring, invalidation, implementation, profiling) to reach starting point (thought 1: define requirements) - Tip: Begin with the desired outcome, then repeatedly ask "what must be true immediately before this?" **Mixed/Branched Thinking**: Combine approaches or explore alternative paths using branch parameters - Use when: Complex problems requiring multiple perspectives or hypothesis testing - Pattern: Use isRevision, branchFromThought, and branchId to create alternative reasoning paths Patterns Cookbook: The patterns cookbook guide is automatically provided as an embedded resource at thought 1 and at the final thought. You can also request it at any time using the includeGuide parameter. The cookbook contains 20+ reasoning patterns with examples and usage guidance. Key features: - You can adjust total_thoughts up or down as you progress - You can question or revise previous thoughts - You can add more thoughts even after reaching what seemed like the end - You can express uncertainty and explore alternative approaches - Not every thought needs to build linearly - you can branch or backtrack - Generates a solution hypothesis - Verifies the hypothesis based on the Chain of Thought steps - Repeats the process until satisfied - Provides a correct answer Parameters explained: - thought: Your current thinking step, which can include: * Regular analytical steps * Revisions of previous thoughts * Questions about previous decisions * Realizations about needing more analysis * Changes in approach * Hypothesis generation * Hypothesis verification - next_thought_needed: True if you need more thinking, even if at what seemed like the end - thought_number: Current number in sequence (can go beyond initial total if needed) - total_thoughts: Current estimate of thoughts needed (can be adjusted up/down) - is_revision: A boolean indicating if this thought revises previous thinking - revises_thought: If is_revision is true, which thought number is being reconsidered - branch_from_thought: If branching, which thought number is the branching point - branch_id: Identifier for the current branch (if any) - needs_more_thoughts: If reaching end but realizing more thoughts needed You should: 1. Start with an initial estimate of needed thoughts, but be ready to adjust 2. Feel free to question or revise previous thoughts 3. Don't hesitate to add more thoughts if needed, even at the "end" 4. Express uncertainty when present 5. Mark thoughts that revise previous thinking or branch into new paths 6. Ignore information that is irrelevant to the current step 7. Generate a solution hypothesis when appropriate 8. Verify the hypothesis based on the Chain of Thought steps 9. Repeat the process until satisfied with the solution 10. Provide a single, ideally correct answer as the final output 11. Only set next_thought_needed to false when truly done and a satisfactory answer is reached. It is categorised as a Destructive tool in the Clear Thought 1 5 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Add a rule in your Intercept YAML policy under the tools section for clear_thought. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Clear Thought 1 5 MCP server.
clear_thought is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_thought rule in your Intercept 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 Intercept policy for clear_thought. 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.
clear_thought is provided by the Clear Thought 1 5 MCP server (waldzellai/clear-thought). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept