mindwiki_request_proposal_apply

Relay an in-chat user approval to apply an apply_ready proposal. For safe_additive proposals the apply runs immediately and the user's words are recorded as audit evidence. For safe_structural and higher the response asks the user to approve in the MindWiki app — the AI initiated the request but the apply itself requires the user's own trusted surface. Always re-validates the proposal server-side; drift returns needs_refresh with zero writes.

Access

Requires write access and the corresponding vault agent permission. MCP access requires Pro or Power. See Authentication for OAuth versus API key scopes.

Input schema

{
  "type": "object",
  "properties": {
    "proposal_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Existing apply_ready proposal id."
    },
    "user_decision_evidence": {
      "type": "string",
      "maxLength": 2000,
      "description": "The user's actual words approving the apply, e.g. 'yes apply it'. Stored as audit evidence \u2014 the risk tier and channel are the authorization, not this string."
    },
    "agent": {
      "type": "string",
      "maxLength": 200,
      "description": "Optional assistant or client name to record as relayed_by, such as 'Claude Desktop'. Defaults to a generic external-assistant label."
    }
  },
  "required": [
    "proposal_id"
  ],
  "additionalProperties": false
}

Client use

Call this tool through tools/call at https://api.mindwiki.io/mcp after initialization and authentication. Check the tool result for errors before reporting success. A proposal creation or apply request is not itself proof that a change was applied; inspect the returned status and verify the result in MindWiki.

See MCP Tools for the complete catalog and Muse for connector availability.