Medium Risk

setHeliusApiKey

Set an existing Helius API key for the current session. If the user does not have a key, use the agentic signup flow instead: generateKeypair → fund wallet → agenticSignup. Get a key at https://dashboard.helius.dev/api-keys

Handles credentials or secrets (apiKey)

Part of the Helius MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

helius-mcp Write

AI agents use setHeliusApiKey to create or modify resources in Helius. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call setHeliusApiKey repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Helius.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

helius.yaml
tools:
  setHeliusApiKey:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Helius policy for all 63 tools.

Tool Name setHeliusApiKey
Category Write
MCP Server Helius MCP Server
Risk Level Medium

View all 63 tools →

Agents calling write-class tools like setHeliusApiKey have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the setHeliusApiKey tool do? +

Set an existing Helius API key for the current session. If the user does not have a key, use the agentic signup flow instead: generateKeypair → fund wallet → agenticSignup. Get a key at https://dashboard.helius.dev/api-keys. It is categorised as a Write tool in the Helius MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on setHeliusApiKey? +

Add a rule in your Intercept YAML policy under the tools section for setHeliusApiKey. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Helius MCP server.

What risk level is setHeliusApiKey? +

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

Can I rate-limit setHeliusApiKey? +

Yes. Add a rate_limit block to the setHeliusApiKey rule in your Intercept 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 setHeliusApiKey completely? +

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

setHeliusApiKey is provided by the Helius MCP server (helius-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.