export_keystore

Export an encrypted keystore file (Argon2id KDF) for a wallet address.

SERVERTenzro Ledger MCP SOURCEhttps://canton-mcp.tenzro.network/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/network-tenzro-tenzro/export-keystore.md

WHAT IT DOES

What export_keystore does on Tenzro Ledger MCP

AI agents call export_keystore to retrieve information from Tenzro Ledger MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why export_keystore is rated Low

This tool exports a keystore file containing encrypted private key material for a wallet. While it is technically a read/retrieval operation (no data is modified), the blast radius is very high: if the encrypted keystore is obtained by a malicious actor, it could lead to full wallet compromise. The Argon2id KDF offers some protection, but exporting key material is inherently sensitive.

From the tool's definition Export an encrypted keystore file (Argon2id KDF) for a wallet address.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs export_keystore safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tenzro Ledger MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For export_keystore, this is the rule to start with:

export_keystore Allowed

export_keystore is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_keystore": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every export_keystore call is checked against it from then on.

FAQ

Questions about export_keystore

What does the export_keystore tool do? +

Export an encrypted keystore file (Argon2id KDF) for a wallet address. It is categorised as a Read tool in the Tenzro Ledger MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on export_keystore? +

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

What risk level is export_keystore? +

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

Can I rate-limit export_keystore? +

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

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

export_keystore is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tenzro Ledger, and thousands of servers like it.

This server

All 360 Tenzro Ledger tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →