Low Risk

derive_wallet

Derive an EVM + Solana wallet from a BIP39 mnemonic at a given account index (BIP44 path)

How to control derive_wallet ↓

AI agents call derive_wallet to retrieve information from Agenti without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Even though derive_wallet only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Documented attack patterns abuse exactly the kind of access derive_wallet gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Agenti, and nothing reaches the server without passing your rules. This is the rule we recommend for derive_wallet:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "derive_wallet": {}
  }
}

derive_wallet is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Agenti — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the derive_wallet tool do? +

Derive an EVM + Solana wallet from a BIP39 mnemonic at a given account index (BIP44 path). It is categorised as a Read tool in the Agenti MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on derive_wallet? +

Register the Agenti MCP server in PolicyLayer and add a rule for derive_wallet: 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 Agenti. Nothing to install.

What risk level is derive_wallet? +

derive_wallet is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit derive_wallet? +

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

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

derive_wallet is provided by the Agenti MCP server (nirholas/agenti). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Agenti tool call.

Deterministic rules across all 73 Agenti tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

73 Agenti tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.