Export an encrypted keystore file (Argon2id KDF) for a wallet address.
AI agents call export_keystore to retrieve information from Tenzro Ledger MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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
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.
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.
export_keystore is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →