set_helius_api_key

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Medium RISK CLASS

Category Write

Parameters 11 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/set-helius-api-key.md

WHAT IT DOES

What set_helius_api_key does on VaultPilot MCP

AI agents use set_helius_api_key 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	Description
`apiKey`	string	Yes	Helius API key (UUID format: 8-4-4-4-12 hex chars). Get one for free at https://dashboard.helius.dev/. Pass the bare key — the server constructs the canonical H

Parameters from the server's own tool schema.

RISK

Why set_helius_api_key is rated Medium

This tool creates or modifies configuration state (the Solana RPC endpoint and credentials) that affects all subsequent blockchain operations. While not destructive or financial by itself, it irreversibly changes the server's behavior until restart and could redirect blockchain queries to attacker-controlled infrastructure if misused by a compromised agent.

From the tool's definition Tool description states it 'Set[s] a Helius API key' and 'constructs the canonical Helius mainnet URL internally and uses it for every subsequent Solana call' — this modifies runtime configuration that persists across multiple operations.

Risk signalsHandles credentials or secrets (apiKey) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

set_helius_api_key Rate-limited

set_helius_api_key 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": {
    "set_helius_api_key": {
      "limits": [
        {
          "counter": "set_helius_api_key_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 set_helius_api_key call is checked against it from then on.

FAQ

Questions about set_helius_api_key

What does the set_helius_api_key tool do? +

Set a Helius API key for Solana RPC reads at runtime — no restart required. The server constructs the canonical Helius mainnet URL (https://mainnet.helius-rpc.com/?api-key=<KEY>) internally and uses it for every subsequent Solana call until the process restarts. Takes precedence over SOLANA_RPC_URL env var and userConfig. Designed for the demo-mode flow where users want to fix Solana rate-limits without restarting their MCP client, but works in any mode. INPUT: bare API key only (UUID format, 8-4-4-4-12 hex). Pasting a URL is rejected to prevent prompt-injection redirects to malicious endpoints. WHERE TO GET ONE: https://dashboard.helius.dev/ — sign in (GitHub or email), copy the default API key auto-created on first login. Free tier covers personal-volume Solana reads + writes. PERSISTENCE: process memory only. To save across restarts, run vaultpilot-mcp-setup (after exiting demo mode if applicable) and pick "Solana RPC URL" — paste the same key there. AGENT BEHAVIOR: when the user pastes a key in chat ('here's my Helius key: <uuid>'), call this tool immediately. NEVER echo the key back in any subsequent response — treat it as secret-shaped even though Helius keys can be regenerated. 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 set_helius_api_key accept? +

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

How do I enforce a policy on set_helius_api_key? +

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

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

Can I rate-limit set_helius_api_key? +

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

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

set_helius_api_key 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

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

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