list_readonly_invites
List the read-only share tokens the user has generated. By default returns only ACTIVE invites (not revoked, not expired); pass includeInactive: true to see history. Each entry returns { id, name, scope, issuedAt, expiresAt, revokedAt, expired, active, walletCounts, totalAddresses } — note the ad...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/list-readonly-invites.md
What list_readonly_invites does on VaultPilot MCP
AI agents call list_readonly_invites 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 |
|---|---|---|---|
includeInactive | boolean | — |
Parameters from the server's own tool schema.
Why list_readonly_invites is rated Low
This is a pure read operation that queries and lists existing read-only share tokens. It retrieves metadata about invitations the user has created but does not modify, execute, delete, or transfer any assets. The tool is explicitly marked as 'Read-only' and has no capability to create, revoke, or affect financial transactions.
From the tool's definition Tool description explicitly states "List the read-only share tokens" and "Read-only." Returns metadata about invites (id, name, scope, issuedAt, expiresAt, revokedAt, expired, active, walletCounts, totalAddresses) but explicitly notes that "the addresses…
Attacks that exploit this kind of access
The rule that runs list_readonly_invites 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 list_readonly_invites, this is the rule to start with:
list_readonly_invites 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 list_readonly_invites call is checked against it from then on.
Questions about list_readonly_invites
List the read-only share tokens the user has generated. By default returns only ACTIVE invites (not revoked, not expired); pass includeInactive: true to see history. Each entry returns { id, name, scope, issuedAt, expiresAt, revokedAt, expired, active, walletCounts, totalAddresses } — note the addresses themselves are NOT re-surfaced here, only counts per chain (the raw token isn't stored either, only its sha256 hash). Pair with revoke_readonly_invite({ name }) to invalidate an invite. Read-only. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
list_readonly_invites accepts 1 parameter: includeInactive. 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 list_readonly_invites: 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.
list_readonly_invites 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 list_readonly_invites 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 list_readonly_invites. 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.
list_readonly_invites 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