Connectors · MSP & PSA
Azure Key Vault MCP server for AI agents.
actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Azure Key Vault and the rest of your systems. It gives your agent 86 Azure Key Vault actions (44 reads, 28 writes and 14 that wait for a confirmation) and holds the Azure Key Vault credential itself, so the agent never does. It paces Azure Key Vault's limits and records every call.
100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.
claude mcp add --transport http actionlake https://connect.actionlake.com/mcpdo { action: "azure_key_vault.certificates.list", intent: "check which Azure Key Vault account is connected"}# List certificates in a specified key vault · read · 1 upstream call- 86actionsin one signed file
- 44readlook, never change
- 28writecreate and update
- 14wait for a yesdestructive, confirmed first
Set up
Connect Azure Key Vault in three steps.
- 01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp - 02
Connect Azure Key Vault.
OAuth 2.0, client credentials. Paste the app's client id and secret; actionlake fetches and renews the token, and nobody has to sign in. actionlake stores what you paste write-only, sealed under your tenant's key.
client_idEntra application (client) id of a service principal granted a Key Vault data role (or access policy) on the vaultclient_secretEntra client secrethostWhere your Azure Key Vault lives: your hosttenant_idYour Azure Key Vault tenant id
account { op: "connections.requirements", service: "azure_key_vault" } # free: exactly what to paste, and what is found for you - 03
Make the first call. Check before a write.
Ask in plain words; Claude picks the action. Before anything changes,
checkvalidates the call and prices it, for free.do { action: "azure_key_vault.certificates.list" }# list certificates in a specified key vault · read · 1 upstream callcheck { action: "azure_key_vault.certificates.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent
Azure Key Vault at a glance
- Sign-in
- OAuth 2.0, client credentials. Paste the app's client id and secret; actionlake fetches and renews the token, and nobody has to sign in.
- You provide
client_idclient_secret- Setup fields
hosttenant_id- Limits we pace to
- 1,000 calls per 10 seconds, per connection
- API covered
- Azure Key Vault (secrets, keys and cryptographic operations, certificates, issuers, soft-delete recovery) API Azure Key Vault data plane: Secrets 2026-04-01, Keys 2026-04-01, Certificates 2026-04-01, Storage 7.4, at your Azure Key Vault instance's API base URL, which you enter when connecting
- Built from
- Azure Key Vault's documentation, read 23 October 2026OpenAPI spec (GitHub)OpenAPI spec (GitHub)OpenAPI spec (GitHub)
- Service file
- Version 1.0.0, signed (Ed25519)
- Cached reads
- 25 of 44 reads, for up to 5 minutes; a write clears what it affects
- Shared entities
- 1, so ask can line Azure Key Vault up with your other systems
- Data
- Processed and stored in Sydney, Australia. No US region yet
Capabilities
What an AI agent can do in Azure Key Vault.
86 actions in 13 areas. Every one carries its effect, so a key can allow the reads and hold the rest.
- 44readlook, never change
- 28writecreate and update
- 14destructivewait for a confirmation
Keys
2316 read · 5 write · 2 destructive
List keys in the specified vault · Gets the public part of a stored key · Creates a new key, stores it, then returns key parameters and attributes to the client · The update key operation changes specified attributes of a stored key and can be applied to any key type and key version stored in Azure Key Vault
Certificates
115 read · 5 write · 1 destructive
List certificates in a specified key vault · Gets information about a certificate · Creates a new certificate · Updates the specified attributes associated with the given certificate
Secrets
84 read · 3 write · 1 destructive
List secrets in a specified key vault · Get a specified secret from a given key vault · Updates the attributes associated with a specified secret in a given key vault · Deletes a secret from a specified key vault
Storage accounts
83 read · 3 write · 2 destructive
List storage accounts managed by the specified key vault · Gets information about a specified storage account · Backs up the specified storage account · Restores a backed up storage account to a vault
Certificate issuers
52 read · 2 write · 1 destructive
List certificate issuers for a specified key vault · Lists the specified certificate issuer · Updates the specified certificate issuer · Deletes the specified certificate issuer
Sas definitions
52 read · 2 write · 1 destructive
List storage SAS definitions for the given storage account · Gets information about an SAS definition for the specified storage account · Updates the specified attributes associated with the given SAS definition · Deletes an SAS definition from a specified storage account
Certificate operations
41 read · 2 write · 1 destructive
Gets the creation operation of a certificate · Merges a certificate or a certificate chain with a key pair existing on the server · Updates a certificate operation · Deletes the creation operation for a specific certificate
Deleted certificates
42 read · 1 write · 1 destructive
Lists the deleted certificates in the specified vault currently available for recovery · Retrieves information about the specified deleted certificate · Recovers the deleted certificate back to its current version under /certificates · Permanently deletes the specified deleted certificate
5 more areas · 18 actions
- Deleted keys 4
- Deleted secrets 4
- Deleted storage accounts 4
- Certificate contacts 3
- Deleted sas definitions 3
Top actions
The Azure Key Vault API, shaped for agents.
The ids your agent types, what each does, and the one name it shares with other systems. 15 of Azure Key Vault's 16 action names are shared with at least one other connector, so an agent learns them once.
| Action | What it does | Effect | Same name in |
|---|---|---|---|
azure_key_vault.certificates.listList certificates in a specified key vault | List certificates in a specified key vault. | read | security.certificate.list22 connectors |
azure_key_vault.secrets.listList secrets in a specified key vault | List secrets in a specified key vault. | read | security.secret.list21 connectors |
azure_key_vault.secrets.getGet a specified secret from a given key vault | Get a specified secret from a given key vault. | read | security.secret.get21 connectors |
azure_key_vault.certificates.getGets information about a certificate | Gets information about a certificate. | read | security.certificate.get20 connectors |
azure_key_vault.keys.listList keys in the specified vault | List keys in the specified vault. | read | security.encryption_key.list5 connectors |
azure_key_vault.keys.getGets the public part of a stored key | Gets the public part of a stored key. | read | security.encryption_key.get9 connectors |
azure_key_vault.certificates.createCreates a new certificate | Creates a new certificate. | write | security.certificate.create15 connectors |
azure_key_vault.secrets.updateUpdates the attributes associated with a specified secret in a given key vault | Updates the attributes associated with a specified secret in a given key vault. | write | security.secret.update16 connectors |
azure_key_vault.keys.createCreates a new key, stores it, then returns key parameters and attributes to the client | Creates a new key, stores it, then returns key parameters and attributes to the client. | write | security.encryption_key.create6 connectors |
azure_key_vault.secrets.deleteDeletes a secret from a specified key vault | Deletes a secret from a specified key vault. | destructive | security.secret.delete23 connectors |
azure_key_vault.deleted_keys.listLists the deleted keys in the specified vault | Lists the deleted keys in the specified vault. | read | this connector |
azure_key_vault.keys.list_versionsRetrieves a list of individual key versions with the same key name | Retrieves a list of individual key versions with the same key name. | read | this connector |
Try it
Prompts to paste into Claude.
Each one names the Azure Key Vault actions it will call, so you know what it reads and what it changes before you send it.
- Readread
List certificates in a specified key vault in Azure Key Vault and tell me what stands out.
calls
azure_key_vault.certificates.list - Writewrite
Creates a new certificate in Azure Key Vault. Show me exactly what you will send before you save it.
calls
azure_key_vault.certificates.create
Governance for Azure Key Vault
Destructive actions wait for a yes.
14 Azure Key Vault actions are destructive. These are all of them:
- Deletes a secret from a specified key vault
azure_key_vault.secrets.delete - Deletes a certificate from a specified key vault
azure_key_vault.certificates.delete - Deletes a key of any type from storage in Azure Key Vault
azure_key_vault.keys.delete - Creates a new key version, stores it, then returns key parameters, attributes and policy to the client
azure_key_vault.keys.rotate - Regenerates the specified key value for the given storage account
azure_key_vault.storage_accounts.regenerate_key - Permanently deletes the specified key
azure_key_vault.deleted_keys.purge - Permanently deletes the specified secret
azure_key_vault.deleted_secrets.purge - Deletes an SAS definition from a specified storage account
azure_key_vault.sas_definitions.delete - Deletes a storage account
azure_key_vault.storage_accounts.delete - Deletes the specified certificate issuer
azure_key_vault.certificate_issuers.delete - Permanently deletes the specified deleted certificate
azure_key_vault.deleted_certificates.purge - Deletes the certificate contacts for a specified key vault
azure_key_vault.certificate_contacts.delete - Deletes the creation operation for a specific certificate
azure_key_vault.certificate_operations.delete - Permanently deletes the specified storage account
azure_key_vault.deleted_storage_accounts.purge
A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.
Deletes a secret from a specified key vault?
intent: the user asked me to deletes a secret from a specified key vault
account { op: "keys.create", name: "azure-key-vault-agent", allowed_actions: ["azure_key_vault.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "azure_key_vault.secrets.delete", approver: "[email protected]" }, { match: "azure_key_vault.certificates.delete", approver: "[email protected]" }, { match: "azure_key_vault.keys.delete", approver: "[email protected]" } ]}Cost
What Azure Key Vault costs on actionlake.
Every Azure Key Vault action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Azure Key Vault refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
- 1upstream call per actionall 86 Azure Key Vault actions
- 14actions pageeach page of a long list is one call
- 25reads can be cacheda cache hit costs nothing
- 100,000calls a month, freepaid plans from US$49 a month for 250,000
Action index
Every Azure Key Vault action.
86 actions by area: the id your agent calls, what it does, and its effect.
Keys23
azure_key_vault.keys.backupRequests that a backup of the specified key be downloaded to the clientreadazure_key_vault.keys.createCreates a new key, stores it, then returns key parameters and attributes to the clientwriteazure_key_vault.keys.decryptDecrypts a single block of encrypted datareadazure_key_vault.keys.deleteDeletes a key of any type from storage in Azure Key Vaultdestructiveazure_key_vault.keys.encryptEncrypts an arbitrary sequence of bytes using an encryption key that is stored in a key vaultreadazure_key_vault.keys.getGets the public part of a stored keyreadazure_key_vault.keys.get_attestationGets the public part of a stored key along with its attestation blobreadazure_key_vault.keys.get_random_bytesGet the requested number of bytes containing random valuesreadazure_key_vault.keys.get_rotation_policyLists the policy for a keyreadazure_key_vault.keys.importImports an externally created key, stores it, and returns key parameters and attributes to the clientwriteazure_key_vault.keys.listList keys in the specified vaultreadazure_key_vault.keys.list_versionsRetrieves a list of individual key versions with the same key namereadazure_key_vault.keys.releaseReleases a keyreadazure_key_vault.keys.restoreRestores a backed up key to a vaultwriteazure_key_vault.keys.rotateCreates a new key version, stores it, then returns key parameters, attributes and policy to the clientdestructiveazure_key_vault.keys.secure_unwrap_keySecurely unwraps a previously wrapped symmetric key using a specified key, ensuring TEE attestation via Microsoft Azure Attestation (MAA) before unwrappingreadazure_key_vault.keys.secure_wrap_keyCreates a new 256 bit AES key within the trusted execution environment and wraps this key using a specified keyreadazure_key_vault.keys.signCreates a signature from a digest using the specified keyreadazure_key_vault.keys.unwrap_keyUnwraps a symmetric key using the specified key that was initially used for wrapping that keyreadazure_key_vault.keys.updateThe update key operation changes specified attributes of a stored key and can be applied to any key type and key version stored in Azure Key Vaultwriteazure_key_vault.keys.update_rotation_policyUpdates the rotation policy for a keywriteazure_key_vault.keys.verifyVerifies a signature using a specified keyreadazure_key_vault.keys.wrap_keyWraps a symmetric key using a specified keyread
Certificates11
azure_key_vault.certificates.backupBacks up the specified certificatereadazure_key_vault.certificates.createCreates a new certificatewriteazure_key_vault.certificates.deleteDeletes a certificate from a specified key vaultdestructiveazure_key_vault.certificates.getGets information about a certificatereadazure_key_vault.certificates.get_policyLists the policy for a certificatereadazure_key_vault.certificates.importImports a certificate into a specified key vaultwriteazure_key_vault.certificates.listList certificates in a specified key vaultreadazure_key_vault.certificates.list_versionsList the versions of a certificatereadazure_key_vault.certificates.restoreRestores a backed up certificate to a vaultwriteazure_key_vault.certificates.updateUpdates the specified attributes associated with the given certificatewriteazure_key_vault.certificates.update_policyUpdates the policy for a certificatewrite
Secrets8
azure_key_vault.secrets.backupBacks up the specified secretreadazure_key_vault.secrets.deleteDeletes a secret from a specified key vaultdestructiveazure_key_vault.secrets.getGet a specified secret from a given key vaultreadazure_key_vault.secrets.listList secrets in a specified key vaultreadazure_key_vault.secrets.list_versionsList all versions of the specified secretreadazure_key_vault.secrets.restoreRestores a backed up secret to a vaultwriteazure_key_vault.secrets.setSets a secret in a specified key vaultwriteazure_key_vault.secrets.updateUpdates the attributes associated with a specified secret in a given key vaultwrite
Storage accounts8
azure_key_vault.storage_accounts.backupBacks up the specified storage accountreadazure_key_vault.storage_accounts.deleteDeletes a storage accountdestructiveazure_key_vault.storage_accounts.getGets information about a specified storage accountreadazure_key_vault.storage_accounts.listList storage accounts managed by the specified key vaultreadazure_key_vault.storage_accounts.regenerate_keyRegenerates the specified key value for the given storage accountdestructiveazure_key_vault.storage_accounts.restoreRestores a backed up storage account to a vaultwriteazure_key_vault.storage_accounts.setCreates or updates a new storage accountwriteazure_key_vault.storage_accounts.updateUpdates the specified attributes associated with the given storage accountwrite
Certificate issuers5
azure_key_vault.certificate_issuers.deleteDeletes the specified certificate issuerdestructiveazure_key_vault.certificate_issuers.getLists the specified certificate issuerreadazure_key_vault.certificate_issuers.listList certificate issuers for a specified key vaultreadazure_key_vault.certificate_issuers.setSets the specified certificate issuerwriteazure_key_vault.certificate_issuers.updateUpdates the specified certificate issuerwrite
Sas definitions5
azure_key_vault.sas_definitions.deleteDeletes an SAS definition from a specified storage accountdestructiveazure_key_vault.sas_definitions.getGets information about an SAS definition for the specified storage accountreadazure_key_vault.sas_definitions.listList storage SAS definitions for the given storage accountreadazure_key_vault.sas_definitions.setCreates or updates a new SAS definition for the specified storage accountwriteazure_key_vault.sas_definitions.updateUpdates the specified attributes associated with the given SAS definitionwrite
Certificate operations4
azure_key_vault.certificate_operations.deleteDeletes the creation operation for a specific certificatedestructiveazure_key_vault.certificate_operations.getGets the creation operation of a certificatereadazure_key_vault.certificate_operations.mergeMerges a certificate or a certificate chain with a key pair existing on the serverwriteazure_key_vault.certificate_operations.updateUpdates a certificate operationwrite
Deleted certificates4
azure_key_vault.deleted_certificates.getRetrieves information about the specified deleted certificatereadazure_key_vault.deleted_certificates.listLists the deleted certificates in the specified vault currently available for recoveryreadazure_key_vault.deleted_certificates.purgePermanently deletes the specified deleted certificatedestructiveazure_key_vault.deleted_certificates.recoverRecovers the deleted certificate back to its current version under /certificateswrite
Deleted keys4
azure_key_vault.deleted_keys.getGets the public part of a deleted keyreadazure_key_vault.deleted_keys.listLists the deleted keys in the specified vaultreadazure_key_vault.deleted_keys.purgePermanently deletes the specified keydestructiveazure_key_vault.deleted_keys.recoverRecovers the deleted key to its latest versionwrite
Deleted secrets4
azure_key_vault.deleted_secrets.getGets the specified deleted secretreadazure_key_vault.deleted_secrets.listLists deleted secrets for the specified vaultreadazure_key_vault.deleted_secrets.purgePermanently deletes the specified secretdestructiveazure_key_vault.deleted_secrets.recoverRecovers the deleted secret to the latest versionwrite
Deleted storage accounts4
azure_key_vault.deleted_storage_accounts.getGets the specified deleted storage accountreadazure_key_vault.deleted_storage_accounts.listLists deleted storage accounts for the specified vaultreadazure_key_vault.deleted_storage_accounts.purgePermanently deletes the specified storage accountdestructiveazure_key_vault.deleted_storage_accounts.recoverRecovers the deleted storage accountwrite
Certificate contacts3
azure_key_vault.certificate_contacts.deleteDeletes the certificate contacts for a specified key vaultdestructiveazure_key_vault.certificate_contacts.getLists the certificate contacts for a specified key vaultreadazure_key_vault.certificate_contacts.setSets the certificate contacts for the specified key vaultwrite
Deleted sas definitions3
azure_key_vault.deleted_sas_definitions.getGets the specified deleted sas definitionreadazure_key_vault.deleted_sas_definitions.listLists deleted SAS definitions for the specified vault and storage accountreadazure_key_vault.deleted_sas_definitions.recoverRecovers the deleted SAS definitionwrite
Questions
The Azure Key Vault MCP server, answered.
Is there an Azure Key Vault MCP server for Claude?
Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 86 Azure Key Vault actions across keys, certificates, secrets and storage accounts, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Azure Key Vault.
What do I need to connect Azure Key Vault?
Entra application (client) id of a service principal granted a Key Vault data role (or access policy) on the vault and Entra client secret. Plus your host and your tenant id. The free call account { op: "connections.requirements", service: "azure_key_vault" } lists exactly what to paste.
Can an AI agent delete or change things in Azure Key Vault?
Only if its key allows it, and only with an explicit confirmation. 14 Azure Key Vault actions are destructive, including deletes a secret from a specified key vault, deletes a certificate from a specified key vault and deletes a key of any type from storage in Azure Key Vault. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.
Will an AI agent use up my Azure Key Vault API limit?
actionlake paces every call to the limits in the Azure Key Vault service file: 1,000 calls per 10 seconds per connection. Repeated reads are answered from cache (25 Azure Key Vault actions can be), which never reaches Azure Key Vault.
What does an Azure Key Vault action cost?
One upstream call, the only unit actionlake bills. A list that pages bills one call per page (14 Azure Key Vault actions page). Cache hits, searches, dry runs and calls Azure Key Vault refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
Which Azure Key Vault API does it cover?
The Azure Key Vault (secrets, keys and cryptographic operations, certificates, issuers, soft-delete recovery) API Azure Key Vault data plane: Secrets 2026-04-01, Keys 2026-04-01, Certificates 2026-04-01, Storage 7.4 at your Azure Key Vault instance's API base URL, which you enter when connecting. It is built from Azure Key Vault's documentation as read on 23 October 2026. 86 actions in 13 areas, each one in the signed service file (version 1.0.0).
Does actionlake keep my Azure Key Vault data, and where?
actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Azure Key Vault credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.
Which AI clients can use it?
Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.
Give your agent Azure Key Vault today.
Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.
