// MCP TOOL REFERENCE

M3 MEMORY TOOLS

43 tools from the M3 Memory MCP Server, categorised by risk level.

// ALL 43 M3 MEMORY TOOLS

READ 23 tools

Read check_thermal_load Checks the system thermal pressure level (Protocol #2). Read debug_analyze Root cause analysis with memory-augmented reasoning. Read debug_correlate Cross-reference logs and decisions. Read debug_history Search past debugging sessions. Read debug_trace Execution flow analysis — reads source, finds callers. Read files_corpus_get Fetch a single corpus's settings + counts. Read files_corpus_list Enumerate corpora with row counts. Read files_dedup Scan leaf embeddings for near-duplicates. Detection only — Read files_dedup_list List near-duplicate candidate pairs with text snippets and paths. Read files_entity_coalesce Detect provisional-entity coalescing candidates (quarantine noise + Read files_entity_coalesce_list List entity-coalescing candidate pairs (name + score + band). Read files_get Fetch one record by UUID. Tries file_nodes then leaves. Read files_index Return file-level summaries for triage. Read files_promotable List top promotion candidates by usage-weighted heuristic score. Read files_promotion_list List existing promotions. source_superseded=True surfaces Read files_search Hybrid FTS5 + vector search over leaves. Read files_staleness_review Compare filesystem against files.db. Surfaces stale, touched-only, Read files_stats Corpus-level counters: file_nodes, leaves, embed coverage. Read files_watch_once Single-pass staleness check + notification dispatch. Suitable Read get_news_headlines get_news_headlines Read m3_web_search Alias for web_search. Primary: Perplexity sonar-pro. Fallback: Grok grok-3-latest. Read query_decisions query_decisions Read web_search Searches the live web for current data.

WRITE 13 tools

Write debug_report Generate and persist a structured debugging report. Write files_dedup_review Record a review decision: 'kept' | 'merged' | 'ignored'. Write files_entity_coalesce_review Record review decisions in BULK: pass a list of {uuid, action} where Write files_ingest files_ingest Write log_activity Routes AI data to the correct agent_memory.db table. Write files_corpus_create Register a new corpus with optional default overrides. Write files_corpus_set Update settings for an existing corpus. None args are no-ops. Write files_entity_coalesce_apply files_entity_coalesce_apply Write files_health DB integrity + FTS5 sync check. Set rebuild=True to fix drift. Write files_link_rename Re-point an existing file_node at a new path (rename / move). Write files_promote Promote (ascend) a fact / leaf / file_summary from files.db to Write save_handoff Saves the current AI session state for another agent to resume. Write update_focus Updates the 'Current Focus' ticker for the Pulse dashboard.

DESTRUCTIVE 3 tools

Destructive files_corpus_delete Delete a corpus's settings row. Cascade=True also deletes its Destructive files_entity_coalesce_unapply Reverse one coalescence cluster (drop edges, clear flags, strip Destructive retire_focus Clears the current system focus entry.

EXECUTE 4 tools

Execute debug_bisect Automated git bisect placeholder. Execute files_extract_pending Drain leaves with extraction_status='pending' through the LLM extractor. Execute grok_ask Queries Grok 3 for real-time info from X and fast reasoning. Execute query_local_model Sends a complex reasoning task to the best available local/network LLM.

// FAQ

How many tools does the M3 Memory MCP server have? +

The M3 Memory MCP server exposes 43 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on M3 Memory tools? +

Route the M3 Memory server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do M3 Memory tools fall into? +

M3 Memory tools are categorised as Read (23), Write (13), Destructive (3), Execute (4). Each category has a recommended default policy.

Enforce policy on every M3 Memory tool call.

Start from M3 Memory, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.