generate_readonly_link

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Medium RISK CLASS

Category Write

Parameters 41 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/generate-readonly-link.md

WHAT IT DOES

What generate_readonly_link does on VaultPilot MCP

AI agents use generate_readonly_link to create or update resources in VaultPilot MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VaultPilot MCP environment.

Parameter	Type	Required
`name`	string	—
`scope`	string	—
`wallets`	object	Yes
`expiresIn`	string	—

Parameters from the server's own tool schema.

RISK

Why generate_readonly_link is rated Medium

This tool creates a new access token granting third-party read access to wallet data. It is a Write operation (creating a credential/token) rather than Read, since it produces a persistent artifact with real-world access implications. While the token only grants read-portfolio scope and is time-bound/revocable, misuse could expose sensitive financial position data to unintended parties, warranting medium severity.

From the tool's definition Generate a time-bound, revocable token that lets someone else read a specific subset of the user's wallets via their own VaultPilot instance

Attacks that exploit this kind of access

RECOMMENDED RULE

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

generate_readonly_link Rate-limited

generate_readonly_link stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_readonly_link": {
      "limits": [
        {
          "counter": "generate_readonly_link_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about generate_readonly_link

What does the generate_readonly_link tool do? +

Generate a time-bound, revocable token that lets someone else read a specific subset of the user's wallets via their own VaultPilot instance. The classic use case: hand the token to a financial advisor or experienced friend so they can look at the user's DeFi positions without being given signing access. Pass wallets (at least one of evm / tron / solana / btc arrays — addresses validated against per-chain regex), optional name (auto-defaults to share-XXXX), expiresIn (1h / 24h / 7d / 30d, default 24h), and scope (read-portfolio only in v1). Returns the token ONCE — the issuer-side store keeps only sha256 of the token, so a recipient who paste-bombs the token into a public channel cannot have it re-emitted. Recipient runs import_readonly_token to decode and then queries the wallets via standard portfolio reads (get_portfolio_summary, get_lending_positions, etc.) using their own RPCs. Model A — the token is structured intent, NOT a security boundary: anyone holding it can query the listed addresses, but anyone could query those addresses without it (chain reads are public). Revocation (revoke_readonly_invite) is issuer-side bookkeeping; it doesn't recall a token already in the wild. Use list_readonly_invites to see what's outstanding. Read-only — no signing, no broadcast. It is categorised as a Write tool in the VaultPilot MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does generate_readonly_link accept? +

generate_readonly_link accepts 4 parameters: name, scope, wallets, expiresIn. Required: wallets. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on generate_readonly_link? +

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

generate_readonly_link is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_readonly_link? +

Yes. Add a rate_limit block to the generate_readonly_link 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 generate_readonly_link completely? +

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

generate_readonly_link 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

generate_commit on MCP Server PR Pilot →generate_video_title on YouTube MCP Server →generate_devtools_report on Percepta MCP Server →generate_evidence_manifest on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →