dream_run_now

What dream_run_now does on Enhanced Knowledge Graph Memory Server

AI agents invoke dream_run_now to trigger actions in Enhanced Knowledge Graph Memory Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why dream_run_now is rated High

This tool executes a named operation ('run' is an action verb) that triggers automatic processing within the knowledge graph memory system. While the exact side effects depend on what the dream cycle does (likely memory consolidation, analysis, or optimization based on context), the execution of an autonomous process with non-trivial side effects on stored data qualifies as Execute rather than Read.

From the tool's definition 'Run a single dream cycle immediately' indicates execution of an internal process with defined effects. The tool triggers an operation (dream cycle) that processes and potentially modifies the knowledge graph state based on the server's enhancement features…

The rule that runs dream_run_now safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dream_run_now, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dream_run_now": {
      "limits": [
        {
          "counter": "dream_run_now_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about dream_run_now