Atom of Thoughts (AoT) is a tool for solving complex problems by decomposing them into independent, reusable atomic units of thought. Unlike traditional sequential thinking, this tool enables more powerful problem solving by allowing atomic units of thought to form dependencies with each other. ...
Accepts raw HTML/template content (content)
Part of the Atom of Thoughts MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke AoT to trigger processes or run actions in Atom of Thoughts. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
AoT can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
AoT:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: true See the full Atom of Thoughts policy for all 3 tools.
Agents calling execute-class tools like AoT have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
AoT is one of the high-risk operations in Atom of Thoughts. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Atom of Thoughts (AoT) is a tool for solving complex problems by decomposing them into independent, reusable atomic units of thought. Unlike traditional sequential thinking, this tool enables more powerful problem solving by allowing atomic units of thought to form dependencies with each other. When to use: - Solving problems requiring complex reasoning - Generating hypotheses that need verification from multiple perspectives - Deriving high-confidence conclusions in scenarios where accuracy is crucial - Minimizing logical errors in critical tasks - Decision-making requiring multiple verification steps Atom types: - premise: Basic assumptions or given information for problem solving - reasoning: Logical reasoning process based on other atoms - hypothesis: Proposed solutions or intermediate conclusions - verification: Process to evaluate the validity of other atoms (especially hypotheses) - conclusion: Verified hypotheses or final problem solutions Parameter descriptions: - atomId: Unique identifier for the atom (e.g., 'A1', 'H2') - content: Actual content of the atom - atomType: Type of atom (one of: premise, reasoning, hypothesis, verification, conclusion) - dependencies: List of IDs of other atoms this atom depends on - confidence: Confidence level of this atom (value between 0-1) - isVerified: Whether this atom has been verified - depth: Depth level of this atom (in the decomposition-contraction process) Additional features: 1. Decomposition-Contraction mechanism: - Decompose atoms into smaller sub-atoms and contract back after verification - startDecomposition(atomId): Start atom decomposition - addToDecomposition(decompositionId, atomId): Add sub-atom to decomposition - completeDecomposition(decompositionId): Complete decomposition process 2. Automatic termination mechanism: - Automatically terminate when reaching maximum depth or finding high-confidence conclusion - getTerminationStatus(): Return termination status and reason - getBestConclusion(): Return highest confidence conclusion Usage method: 1. Understand the problem and define necessary premise atoms 2. Create reasoning atoms based on premises 3. Create hypothesis atoms based on reasoning 4. Create verification atoms to verify hypotheses 5. Derive conclusion atoms based on verified hypotheses 6. Use atom decomposition to explore deeper when necessary 7. Present the high-confidence conclusion atom as the final answer. It is categorised as a Execute tool in the Atom of Thoughts MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for AoT. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Atom of Thoughts MCP server.
AoT is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the AoT 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 AoT. 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.
AoT is provided by the Atom of Thoughts MCP server (kbsooo/mcp_atom_of_thoughts). 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