dream_start
Start the DreamEngine background memory maintenance. Runs 8 phases (temporal anchoring, freshness sweep, entropy pruning, consolidation, compression, entity enrichment, pattern promotion, graph hygiene) on a configurable interval.
This record as markdown: /tools/danielsimonjr-memory-mcp/dream-start.md
What dream_start does on Enhanced Knowledge Graph Memory Server
AI agents invoke dream_start 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_start is rated High
This tool executes an automated maintenance operation that modifies the underlying knowledge graph through multiple transformation phases (pruning, consolidation, compression, enrichment). While not immediately destructive (no explicit deletion mentioned), it performs irreversible transformations on stored data (entropy pruning, compression).
From the tool's definition The tool 'Start the DreamEngine background memory maintenance. Runs 8 phases (temporal anchoring, freshness sweep, entropy pruning, consolidation, compression, entity enrichment, pattern promotion, graph hygiene) on a configurable interval.' describes…
Attacks that exploit this kind of access
The rule that runs dream_start 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_start, this is the rule to start with:
dream_start stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every dream_start call is checked against it from then on.
Questions about dream_start
Start the DreamEngine background memory maintenance. Runs 8 phases (temporal anchoring, freshness sweep, entropy pruning, consolidation, compression, entity enrichment, pattern promotion, graph hygiene) on a configurable interval. It is categorised as a Execute tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for dream_start: 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 Enhanced Knowledge Graph Memory Server. Nothing to install.
dream_start 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 dream_start 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.
Set action: deny in the PolicyLayer policy for dream_start. 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.
dream_start is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
Across the catalogue