import_readonly_token
Decode a vp1.… read-only share token (generated by someone else's generate_readonly_link) into the embedded wallet bundle. Accepts either the raw token or an http(s) URL containing a ?t=vp1.… / #t=vp1.… parameter. Returns { wallets, scope, name, issuedAt, expiresAt, id } — the recipient agent the...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/import-readonly-token.md
What import_readonly_token does on VaultPilot MCP
AI agents call import_readonly_token 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 |
|---|---|---|---|
token | string | Yes |
Parameters from the server's own tool schema.
Why import_readonly_token is rated Low
This tool decodes a read-only token and extracts wallet bundle metadata for use in subsequent read operations. It does not write, execute, or move funds. However, severity is medium because it exposes wallet addresses and portfolio scope from a shared token, which could be misused for surveillance or targeted attacks if an agent imports a malicious or forged token.
From the tool's definition 'Decode a vp1.… read-only share token… Returns { wallets, scope, name, issuedAt, expiresAt, id }… recipient agent then passes those wallet addresses to standard portfolio reads'
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
The rule that runs import_readonly_token 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 import_readonly_token, this is the rule to start with:
import_readonly_token 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 import_readonly_token call is checked against it from then on.
Questions about import_readonly_token
Decode a vp1.… read-only share token (generated by someone else's generate_readonly_link) into the embedded wallet bundle. Accepts either the raw token or an http(s) URL containing a ?t=vp1.… / #t=vp1.… parameter. Returns { wallets, scope, name, issuedAt, expiresAt, id } — the recipient agent then passes those wallet addresses to standard portfolio reads (get_portfolio_summary, get_lending_positions, get_token_allowances, get_transaction_history, etc.) using the recipient's own configured RPCs. Refuses expired tokens with a clear error pointing the user back at the issuer. v1 stores nothing recipient-side — the agent juggles addresses in conversation; persistent recipient-side state is deferred. Read-only — no signing, no broadcast. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
import_readonly_token accepts 1 parameter: token. Required: token. 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 import_readonly_token: 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.
import_readonly_token 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 import_readonly_token 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 import_readonly_token. 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.
import_readonly_token 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