mindwiki_request_proposal_reject

Relay an in-chat user rejection of a pending proposal. Always safe to delegate (rejecting destroys no vault content), so this only needs the create_proposals permission, not apply_proposals. Records the user's words in the activity log for audit.

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

json

{
  "type": "object",
  "properties": {
    "proposal_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Existing pending proposal id."
    },
    "user_decision_evidence": {
      "type": "string",
      "maxLength": 2000,
      "description": "The user's actual words rejecting the proposal, e.g. 'no, skip that one'. Stored as audit evidence."
    },
    "agent": {
      "type": "string",
      "maxLength": 200,
      "description": "Optional client name to record as relayed_by. Defaults to a generic external-AI 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.