vault_get
Retrieve and DECRYPT one vault entry's value (returns plaintext to you). Use only when YOU must handle the secret (e.g. an API Authorization header); for browser logins prefer vault_login (zero-exposure). Requires your secret (Bearer).
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/vault-get.md
What vault_get does on Gateway
AI agents call vault_get to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | the entry name |
handle | string | Yes | your registered handle |
Parameters from the server's own tool schema.
Why vault_get is rated Low
This tool retrieves encrypted vault entries and returns them in plaintext. While the data retrieved is highly sensitive (secrets, API keys, credentials), the tool performs only a read operation—no creation, modification, deletion, or code execution occurs.
From the tool's definition Tool description states 'Retrieve and DECRYPT one vault entry's value (returns plaintext to you)' — a retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs vault_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vault_get, this is the rule to start with:
vault_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every vault_get call is checked against it from then on.
Questions about vault_get
Retrieve and DECRYPT one vault entry's value (returns plaintext to you). Use only when YOU must handle the secret (e.g. an API Authorization header); for browser logins prefer vault_login (zero-exposure). Requires your secret (Bearer). It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
vault_get accepts 2 parameters: name, handle. Required: name, handle. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for vault_get: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Gateway. Nothing to install.
vault_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the vault_get rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for vault_get. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
vault_get is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue