get_tx_verification
Re-emit the prepared-tx JSON and VERIFY-BEFORE-SIGNING block for a known handle. Use this when the original prepare_* tool output has dropped out of your context (compaction, long sessions). The response shape and verification block match the original prepare_* call exactly. NEVER recover a verif...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-tx-verification.md
What get_tx_verification does on VaultPilot MCP
AI agents call get_tx_verification to retrieve information from VaultPilot MCP 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 |
|---|---|---|---|
handle | string | Yes | Opaque handle returned by any prepare_* tool. Use this when the original prepare_* response (and its VERIFY-BEFORE-SIGNING block) has been dropped from your con |
Parameters from the server's own tool schema.
Why get_tx_verification is rated Low
This tool reads and retrieves a previously prepared transaction verification block from in-memory state. It has no side effects—it does not create, modify, execute, or delete data.
From the tool's definition Re-emit the prepared-tx JSON and VERIFY-BEFORE-SIGNING block for a known handle. The tool retrieves and displays a stored transaction verification object without modifying, executing, or destroying data.
Attacks that exploit this kind of access
The rule that runs get_tx_verification safely
PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tx_verification, this is the rule to start with:
get_tx_verification 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 VaultPilot MCP, apply this rule, and every get_tx_verification call is checked against it from then on.
Questions about get_tx_verification
Re-emit the prepared-tx JSON and VERIFY-BEFORE-SIGNING block for a known handle. Use this when the original prepare_* tool output has dropped out of your context (compaction, long sessions). The response shape and verification block match the original prepare_* call exactly. NEVER recover a verification block by reading tool-result files from disk — call this tool instead. Handles live in-memory for 15 minutes after issue. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
get_tx_verification accepts 1 parameter: handle. Required: handle. The full parameter table on this page comes from the server's own tool schema.
Register the VaultPilot MCP server in PolicyLayer and add a rule for get_tx_verification: 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 VaultPilot MCP. Nothing to install.
get_tx_verification 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 get_tx_verification 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 get_tx_verification. 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.
get_tx_verification is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on VaultPilot, and thousands of servers like it.
This server
Across the catalogue