get_verification_artifact

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-verification-artifact.md

WHAT IT DOES

What get_verification_artifact does on VaultPilot MCP

AI agents call get_verification_artifact 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. Returns a sparse, copy-paste-friendly JSON artifact carrying the raw calldata (or TRON rawDataHex), chain, recipie

Parameters from the server's own tool schema.

RISK

Why get_verification_artifact is rated Low

While this tool operates in a financial context (crypto transactions), it performs no actual financial operations, state changes, or irreversible actions. It solely retrieves and formats verification data to enable independent review of a prepared transaction before signing. The data returned (raw calldata, hashes, payloadHash) are inspection artifacts intended for verification, not execution.

From the tool's definition Tool returns a verification artifact containing raw calldata, chain info, to/value, payloadHash, and preSignHash; it is a getter that returns data for inspection and verification purposes with no state modifications described.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_verification_artifact 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_verification_artifact, this is the rule to start with:

get_verification_artifact Allowed

get_verification_artifact is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_verification_artifact": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every get_verification_artifact call is checked against it from then on.

FAQ

Questions about get_verification_artifact

What does the get_verification_artifact tool do? +

Return a sparse verification artifact for a prepared tx — raw calldata (or TRON rawDataHex), chain, to/value, payloadHash, preSignHash if preview_send has pinned gas, plus a static prompt instructing a second LLM on how to decode the bytes from scratch. Intended for adversarial independent verification: the user copies this artifact into a second LLM session (different provider recommended) so the second agent produces an independent decode with no shared context from the current conversation. If the two decodes disagree — or if the preSignHash doesn't match what Ledger displays at sign time — the user rejects. Does NOT call any external API; read-only in-memory lookup. Output deliberately omits the server's humanDecode, swiss-knife URL, and 4byte cross-check so the second agent cannot echo them. 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.

What parameters does get_verification_artifact accept? +

get_verification_artifact accepts 1 parameter: handle. Required: handle. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_verification_artifact? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for get_verification_artifact: 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.

What risk level is get_verification_artifact? +

get_verification_artifact is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_verification_artifact? +

Yes. Add a rate_limit block to the get_verification_artifact 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.

How do I block get_verification_artifact completely? +

Set action: deny in the PolicyLayer policy for get_verification_artifact. 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.

What MCP server provides get_verification_artifact? +

get_verification_artifact 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.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →