Helius MCP Policy -- 63 Tools

// TOOL MAP

Read (51) Write / Execute (8) Destructive / Financial (4)

// WHAT CAN GO WRONG

✕

Financial operations (payRenewal, transferSol, transferToken) can move real money. An agent caught in a loop could drain accounts before anyone notices.

✕

Destructive tools (deleteWebhook) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

✕

Write operations (agenticSignup, createWebhook, generateKeypair) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

✕

Execute tools (parseTransactions, recommendStack) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

// RECOMMENDED RULES

Block financial tools by default

payRenewal:
  rules:
    - action: deny

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations

deleteWebhook:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

agenticSignup:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

accountSubscribe:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

// ALL 63 HELIUS TOOLS

FINANCIAL 3 tools

Financial payRenewal Financial transferSol Financial transferToken

DESTRUCTIVE 1 tools

Destructive deleteWebhook

EXECUTE 2 tools

Execute parseTransactions Execute recommendStack

WRITE 6 tools

Write agenticSignup Write createWebhook Write generateKeypair Write setHeliusApiKey Write updateWebhook Write upgradePlan

READ 51 tools

Read accountSubscribe Read batchWalletIdentity Read checkSignupBalance Read compareHeliusPlans Read fetchHeliusBlog Read getAccountInfo Read getAccountStatus Read getAllWebhooks Read getAsset Read getAssetProof Read getAssetProofBatch Read getAssetsByGroup Read getAssetsByOwner Read getBalance Read getBlock Read getEnhancedWebSocketInfo Read getHeliusCreditsInfo Read getHeliusPlanInfo Read getLaserstreamInfo Read getLatencyComparison Read getNetworkStatus Read getNftEditions Read getPriorityFeeEstimate Read getProgramAccounts Read getPumpFunGuide Read getRateLimitInfo Read getSenderInfo Read getSignaturesForAsset Read getSIMD Read getStarted Read getTokenAccounts Read getTokenBalances Read getTokenHolders Read getTransactionHistory Read getWalletBalances Read getWalletFundedBy Read getWalletHistory Read getWalletIdentity Read getWalletTransfers Read getWebhookByID Read getWebhookGuide Read laserstreamSubscribe Read listHeliusDocTopics Read listSIMDs Read lookupHeliusDocs Read previewUpgrade Read readSolanaSourceFile Read searchAssets Read searchSolanaDocs Read transactionSubscribe Read troubleshootError

// FAQ

Can an AI agent move money through the Helius MCP server? +

Yes. The Helius server exposes 3 financial tools including payRenewal, transferSol, transferToken. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. Intercept lets you block financial tools by default or set per-tool rate limits.

Can an AI agent delete data through the Helius MCP server? +

Yes. The Helius server exposes 1 destructive tools including deleteWebhook. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Helius? +

The Helius server has 6 write tools including agenticSignup, createWebhook, generateKeypair. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the Helius MCP server expose? +

63 tools across 5 categories: Destructive, Execute, Financial, Read, Write. 51 are read-only. 12 can modify, create, or delete data.

How do I add Intercept to my Helius setup? +

One line change. Instead of running the Helius server directly, prefix it with Intercept: intercept -c helius.yaml -- npx -y @helius-mcp. Download a pre-built policy from policylayer.com/policies/helius and adjust the limits to match your use case.

// RELATED SERVERS

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

Helius

Other MCP servers with similar tools.

Let agents act without letting them run wild.