Edit

Share via

Azure Confidential Ledger tools for the Azure MCP Server

The Azure MCP Server enables you to manage Azure resources, including Azure Confidential Ledger Services, by using natural language prompts. This capability lets you work with confidential ledger services without needing to remember complex command syntax.

Azure Confidential Ledger is a fully managed, secure, and highly available ledger service that provides a trusted environment for storing sensitive data. It applies trusted execution environments (TEEs) to ensure data integrity and confidentiality, making it suitable for scenarios that require tamper-proof records, such as financial transactions, supply chain management, and compliance auditing.

Note

The Azure MCP Server tools define parameters for data they need to complete tasks. Some of these parameters are specific to each tool and are documented below. Other parameters are global and shared by all tools. For more information, see Tool parameters.

Append an entry to the ledger

Appends an immutable (tamper-proof) entry to a Confidential Ledger instance and returns the transaction identifier.

Example prompts include:

  • Simple data entry: "Append an entry to 'audit-ledger' with data {"key": "value"}"
  • Tamper-proof transaction: "Write a tamper-proof entry to ledger 'financial-ledger' containing {"transaction": "data"}"
  • Collection-specific entry: "Append {"hello": "from tool"} to my confidential ledger 'test-ledger' in collection 'user-data'"
  • Immutable audit log: "Create an immutable ledger entry in 'compliance-ledger' with content {"audit": "log"}"
  • Basic ledger write: "Write an entry to confidential ledger 'business-ledger' with data {"timestamp": "2025-10-08", "event": "user_login"}"
  • Financial transaction: "Append a financial transaction to ledger 'bank-ledger' with content {"amount": 1000, "account": "123456", "type": "deposit"}"
  • Supply chain record: "Write tamper-proof entry to ledger 'supply-chain' with data {"product_id": "ABC123", "location": "warehouse", "status": "shipped"}"
  • Compliance entry: "Create an audit entry in confidential ledger 'regulatory-ledger' in collection 'gdpr-logs' with content {"user_id": "user123", "action": "data_deletion", "timestamp": "2025-10-08T10:30:00Z"}"
  • Security log: "Append security event to ledger 'security-ledger' with data {"event_type": "login_attempt", "ip_address": "192.168.1.1", "success": true}"
  • Document hash: "Write document integrity record to ledger 'document-ledger' in collection 'contracts' with content {"document_id": "contract_001", "hash": "sha256:abc123", "verified": true}"
Parameter Required or optional Description
Ledger Required The name of the Confidential Ledger instance (for example, myledger ).
Content Required The JSON or text payload to append as a tamper-proof ledger entry.
Collection ID Optional Optional ledger collection identifier. If omitted the default collection is used.

Get an entry from the ledger

Retrieves the Confidential Ledger entry and its recorded contents for the specified transaction ID, optionally scoped to a collection.

Example prompts include:

  • Retrieve specific transaction: "Get entry from confidential ledger 'audit-ledger' with transaction ID '2.199'"
  • Collection-specific retrieval: "Get entry with transaction ID '3.275' from ledger 'compliance-ledger' in collection 'gdpr-logs'"
Parameter Required or optional Description
Ledger Required The name of the Confidential Ledger instance (for example, myledger).
Transaction ID Required The Confidential Ledger transaction identifier (for example: 2.199).
Collection ID Optional Optional ledger collection identifier. If omitted the default collection is used.

Related content