Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-vault

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

reveal_secret_via_send

Create an end-to-end encrypted Bitwarden Send one-time URL to share a vault secret securely, with configurable TTL and max views.

Instructions

Reveal a vault secret through a Bitwarden Send, an E2E-encrypted one-time URL. Creates a temporary Send with a configurable TTL and max-views limit. The secret value is encrypted client-side; only the URL fragment (never sent to server) can decrypt it. Blocked when READ_ONLY=1. Logs to DRY_RUN without creating a real Send when DRY_RUN=1.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesExact item name (case-sensitive) of the vault item to reveal.
fieldNoField to reveal. Defaults to "value" (notes for api-key/password/note items, password for login items). Other options: "username", "password", "totp", "notes" (the item notes, e.g. on a login), "uri0" (or uri1, uri2, ...).
max_viewsNoMaximum number of times the Send URL can be accessed. Default 1, range [1, 100].
ttl_secondsNoBitwarden Send TTL in seconds. Default 300 (5 min), range [30, 86400].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.3
    • changedInput schema / properties / field / description
      Previous value: -"Field to reveal. Defaults to \"value\" (notes for api-key/password/note items, password for login items). Other options: \"username\", \"password\", \"totp\", \"uri0\" (or uri1, uri2, ...)."New value: +"Field to reveal. Defaults to \"value\" (notes for api-key/password/note items, password for login items). Other options: \"username\", \"password\", \"totp\", \"notes\" (the item notes, e.g. on a login), \"uri0\" (or uri1, uri2, ...)."
  2. First observedv0.2.2

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations: it explains client-side encryption, that the URL fragment is never sent to the server and is the only decryptor, and that the operation is blocked under READ_ONLY=1 and only logged under DRY_RUN=1. This resolves the apparent tension between the 'reveal' framing and readOnlyHint=false by clarifying it creates a temporary Send rather than mutating the vault item.

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?

Four tight sentences that front-load the purpose, then add security model, then gating flags. No filler; each sentence carries distinct, decision-relevant information.

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?

With no output schema, the description conveys what is produced (a temporary Send URL) and the encryption/expiry model, but does not explicitly state the return shape or where the decryptable fragment is surfaced. For a 4-param tool this is nearly complete.

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

Parameters3/5

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

Schema coverage is 100%, with field, max_views, and ttl_seconds all fully documented including ranges and defaults. The description references configurable TTL and max-views but adds no syntax or format meaning beyond the schema, so baseline 3 applies.

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?

States a specific verb (reveal), resource (vault secret), and mechanism (Bitwarden Send, an E2E-encrypted one-time URL). This clearly distinguishes it from siblings like get_vault_metadata and get_totp_code, which do not create shareable links.

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

Usage Guidelines3/5

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

Describes what the tool does and notes the READ_ONLY=1 block and DRY_RUN behavior, but never states when to prefer this over alternatives such as get_vault_metadata or list_vault_items. Usage is implied rather than explicitly routed.

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

Deploy Server

Other Tools