Module vault 

Vault MCP - the Vaultwarden family (mcp__forge__vault__*).

Thirteen tools, every one held for the reader’s approval: the blocked handler parks a VaultDraft on the workspace registry, the dock draws it, and no operation runs in the vault unless the answer approved it. The card never carries a secret value; a reveal happens only after approval and travels in the tool result.

Re-exports

use std::sync::Arc; 🔒

use forge_primitives::vault::VaultTool; 🔒

use forge_sdk::mcp::server::McpServerBuilder; 🔒

use forge_sdk::mcp::tool::Tool; 🔒

use forge_sdk::mcp::tool::ToolInput; 🔒

use forge_sdk::mcp::tool::ToolOutput; 🔒

use serde::de::DeserializeOwned; 🔒

use serde_json::Value; 🔒

use crate::SessionSlot; 🔒

use crate::mcp::vault::facade::CreateInput; 🔒

use crate::mcp::vault::facade::PatchInput; 🔒

use crate::mcp::vault::facade::VaultFacade; 🔒

use crate::mcp::vault::facade::VaultToolError; 🔒

Modules

facade

The vault family’s facade: the thirteen operations the tools call, every one held for the reader’s approval.

Structs

AttachmentGetArgs 🔒

AttachmentPutArgs 🔒

FolderNameArgs 🔒

FolderUpdateArgs 🔒

GetArgs 🔒

IdArgs 🔒

SearchArgs 🔒

VaultCall 🔒

One tool instance: the family shares a single Tool impl because the name, description and schema are chosen by the tool the instance names.

Functions

add_tools 🔒

Attach the vault tools to an existing McpServerBuilder. Called only when the family is selected AND [vault] is configured, the same double gate systemone uses.

parse 🔒

reply 🔒