remem

Overview Schema Source Related Servers Score Discussions Admin

Govern Memory

govern_memory

Destructive

Manage curated memories by deleting, rejecting, or marking them stale. Preview changes with dry-run before applying auditable, version-checked mutations that preserve raw archive data.

Instructions

Auditably delete, reject, or mark curated memories stale. Use dry_run=true first to preview affected IDs and their current versions. Non-dry-run mutations require confirm_destructive=true, an explicit reason, and expected_versions containing every target ID. This never deletes raw archive data.

Input Schema

TableJSON Schema

Name	Required	Description
`ids`	Yes	Curated memory IDs to mutate. Use dry_run=true first to preview.
`actor`	No	Actor initiating the mutation, e.g. user, codex, claude.
`action`	Yes	Governance action: delete, reject, stale, or acknowledge-pattern.
`reason`	No	Explicit user-visible reason for the mutation.
`dry_run`	No	Preview affected memories without writing status changes or audit events.
`project`	No	Project name filter. Defaults to the MCP process current project.
`expected_versions`	No	Current memory versions keyed by memory ID. Required for every ID in a non-dry-run mutation; obtain them from dry_run=true.
`acknowledge_pattern`	No	Pattern id required when action is acknowledge-pattern, e.g. override_previous_instructions.
`confirm_destructive`	No	Required true for non-dry-run destructive governance mutations.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`action`	Yes
`reason`	Yes
`dry_run`	Yes
`affected`	Yes
`expected_versions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.6.90Sep 5, 2026

addedInput schema / properties / expected_versions

Added value: +{
+  "additionalProperties": false,
+  "description": "Current memory versions keyed by memory ID. Required for every ID in a non-dry-run mutation; obtain them from dry_run=true.",
+  "nullable": true,
+  "patternProperties": {
+    "^-?\\d+$": {
+      "format": "int64",
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / $defs / GovernedMemoryOutput / properties / version
```
Added value: +{
+  "format": "int64",
+  "type": "integer"
+}
```

changedOutput schema / $defs / GovernedMemoryOutput / required

Previous value: -[
-  "id",
-  "title",
-  "previous_status",
-  "new_status"
-]New value: +[
+  "id",
+  "title",
+  "previous_status",
+  "new_status",
+  "version"
+]

addedOutput schema / properties / expected_versions

Added value: +{
+  "additionalProperties": false,
+  "patternProperties": {
+    "^-?\\d+$": {
+      "format": "int64",
+      "type": "integer"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed1 schema field changedv0.6.45Aug 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "GovernedMemoryOutput": {
+      "additionalProperties": false,
+      "properties": {
+        "id": {
+          "format": "int64",
+          "type": "integer"
+        },
+        "new_status": {
+          "type": "string"
+        },
+        "previous_status": {
+          "type": "string"
+        },
+        "title": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "title",
+        "previous_status",
+        "new_status"
+      ],
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "action": {
+      "type": "string"
+    },
+    "affected": {
+      "items": {
+        "$ref": "#/$defs/GovernedMemoryOutput"
+      },
+      "type": "array"
+    },
+    "dry_run": {
+      "type": "boolean"
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "dry_run",
+    "action",
+    "reason",
+    "affected"
+  ],
+  "title": "GovernMemoryOutput",
+  "type": "object"
+}

First observedJul 31, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, but the description adds meaningful behavioral context: mutations are auditable, dry-run previews show affected IDs and versions, non-dry-run mutations require explicit confirmation, and raw archive data is preserved. This goes well beyond what the annotations alone convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three tight sentences with no filler: purpose first, then required workflow, then a scope safeguard. Every sentence carries operational value and the most important safety instruction is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter tool with nested objects and an output schema, the description covers the core workflow, safety requirements, and scope boundary well. The main gap is that the action list omits 'acknowledge-pattern', which is a valid action in the schema and has its own parameter; the schema fills this in, but the description alone would leave an agent unaware of that mode.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds cross-parameter semantics not fully obvious from individual parameter descriptions: dry_run should come first, expected_versions must cover every target ID for non-dry-run, and confirm_destructive is mandatory for destructive writes. This improves an agent's ability to form a correct call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb set ('delete, reject, or mark stale') on a clear resource ('curated memories'), and the phrase 'never deletes raw archive data' distinguishes it from raw-data tools like search_raw and list_raw_sessions. This lets an agent understand the tool's role even before reading the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit procedural guidance: run dry_run=true first, then provide confirm_destructive=true, a reason, and expected_versions for non-dry-run mutations. It also implies a boundary by stating raw archive data is never deleted, which steers agents away from using this tool for that purpose, though it does not name sibling alternatives directly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server