Skip to content
actionlake
Start free

Connectors · Identity & security

Google Secret Manager MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Google Secret Manager and the rest of your systems. It gives your agent 36 Google Secret Manager actions (16 reads, 10 writes and 10 that wait for a confirmation) and holds the Google Secret Manager credential itself, so the agent never does. It paces Google Secret Manager's limits and records every call. Connecting Google Secret Manager needs your own Google Secret Manager OAuth app and one admin sign-in.

Connect Google Secret Manager freeSee pricing

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/mcp
the first call
do {  action: "gcp_secret_manager.locations.list",  intent: "check which Google Secret Manager account is connected"}# Projects locations: list · read · 1 upstream call
  • 36actionsin one signed file
  • 16readlook, never change
  • 10writecreate and update
  • 10wait for a yesdestructive, confirmed first

Set up

Connect Google Secret Manager in three steps.

  1. 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
  2. 02

    Connect Google Secret Manager.

    OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Secret Manager, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. actionlake stores what you paste write-only, sealed under your tenant's key.

    Before the first sign-in, Google Secret Manager needs an OAuth app of your own, registered in its developer portal. actionlake has no Google Secret Manager app to lend you.

    • access_tokenAccess token from one sign-in with your own OAuth app
    • refresh_tokenRefresh token from the same sign-in; the access token is renewed from it
    • client_idGoogle OAuth client id (Google Cloud console > APIs & Services > Credentials; enable the Secret Manager API on the…
    • client_secretGoogle OAuth client secret
    • hostWhere your Google Secret Manager lives: your host
    account { op: "connections.requirements", service: "gcp_secret_manager" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "gcp_secret_manager.locations.list" }# projects locations: list · read · 1 upstream callcheck { action: "gcp_secret_manager.secrets.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Google Secret Manager at a glance

Sign-in
OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Secret Manager, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on.
You provide
access_tokenrefresh_tokenclient_idclient_secret
Setup fields
host
Limits we pace to
600 calls a minute, per connection
API covered
Google Cloud Secret Manager API v1 (secrets, versions, access, rotation, IAM, regional secrets, locations) API secretmanager v1 (Discovery revision 20260925)secretmanager.googleapis.com
Built from
Google Secret Manager's documentation, read 23 October 2026secretmanager.googleapis.comcloud.google.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
2 of 16 reads, for up to 5 minutes; a write clears what it affects
Shared entities
1, so ask can line Google Secret Manager up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Google Secret Manager.

36 actions in 5 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 16readlook, never change
  • 10writecreate and update
  • 10destructivewait for a confirmation

  1. Regional secrets

    11

    4 read · 3 write · 4 destructive

    Projects locations secrets: add version · Projects locations secrets: create · Projects locations secrets: list · Projects locations secrets: test iam permissions

  2. Secrets

    11

    4 read · 3 write · 4 destructive

    Projects secrets: list · Projects secrets: create · Projects secrets: get · Projects secrets: patch

  3. Regional secrets versions

    6

    3 read · 2 write · 1 destructive

    Projects locations secrets versions: list · Projects locations secrets versions: access · Projects locations secrets versions: disable · Projects locations secrets versions: enable

  4. Secrets versions

    6

    3 read · 2 write · 1 destructive

    Projects secrets versions: list · Projects secrets versions: access · Projects secrets versions: disable · Projects secrets versions: enable

  5. Locations

    2

    2 read · 0 write · 0 destructive

    Projects locations: list · Projects locations: get

Top actions

The Google Secret Manager API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 5 of Google Secret Manager's 5 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
gcp_secret_manager.secrets.listProjects secrets: listLists Secrets.readsecurity.secret.list21 connectors
gcp_secret_manager.secrets.createProjects secrets: createCreates a new Secret containing no SecretVersions.writesecurity.secret.create19 connectors
gcp_secret_manager.secrets.deleteProjects secrets: deleteDeletes a Secret.destructivesecurity.secret.delete23 connectors
gcp_secret_manager.secrets.add_versionProjects secrets: add versionCreates a new SecretVersion containing secret data and attaches it to an existing Secret.writethis connector
gcp_secret_manager.secrets.test_iam_permissionsProjects secrets: test iam permissionsReturns permissions that a caller has for the specified secret.readthis connector
gcp_secret_manager.locations.listProjects locations: listLists information about the supported locations for this service.readthis connector
gcp_secret_manager.regional_secrets.listProjects locations secrets: listLists Secrets.readthis connector
gcp_secret_manager.regional_secrets.createProjects locations secrets: createCreates a new Secret containing no SecretVersions.writethis connector

Try it

Prompts to paste into Claude.

Each one names the Google Secret Manager actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Projects locations: list in Google Secret Manager and tell me what stands out.

    callsgcp_secret_manager.locations.list

  2. Writewrite

    Projects secrets: create in Google Secret Manager. Show me exactly what you will send before you save it.

    callsgcp_secret_manager.secrets.create

Governance for Google Secret Manager

Destructive actions wait for a yes.

10 Google Secret Manager actions are destructive. These are all of them:

  • Projects secrets: deletegcp_secret_manager.secrets.delete
  • Projects secrets: rotate secretgcp_secret_manager.secrets.rotate_secret
  • Projects secrets: set iam policygcp_secret_manager.secrets.set_iam_policy
  • Projects secrets: enable managed rotationgcp_secret_manager.secrets.enable_managed_rotation
  • Projects secrets versions: destroygcp_secret_manager.secrets_versions.destroy
  • Projects locations secrets: deletegcp_secret_manager.regional_secrets.delete
  • Projects locations secrets: rotate secretgcp_secret_manager.regional_secrets.rotate_secret
  • Projects locations secrets: set iam policygcp_secret_manager.regional_secrets.set_iam_policy
  • Projects locations secrets: enable managed rotationgcp_secret_manager.regional_secrets.enable_managed_rotation
  • Projects locations secrets versions: destroygcp_secret_manager.regional_secrets_versions.destroy

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.

dogcp_secret_manager.secrets.deleteconfirm_policy: human

Projects secrets: delete?

intent: the user asked me to projects secrets: delete

run suspended · waiting for a named person · key gcp-secret-manager-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "gcp-secret-manager-agent",  allowed_actions: ["gcp_secret_manager.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "gcp_secret_manager.secrets.delete", approver: "[email protected]" },    { match: "gcp_secret_manager.secrets.rotate_secret", approver: "[email protected]" },    { match: "gcp_secret_manager.secrets.set_iam_policy", approver: "[email protected]" }  ]}
Illustrative. Scoped to Google Secret Manager only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Google Secret Manager costs on actionlake.

Every Google Secret Manager action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Google Secret Manager 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 36 Google Secret Manager actions
  • 5actions pageeach page of a long list is one call
  • 2reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Google Secret Manager action.

36 actions by area: the id your agent calls, what it does, and its effect.

Regional secrets11
  • gcp_secret_manager.regional_secrets.add_versionProjects locations secrets: add versionwrite
  • gcp_secret_manager.regional_secrets.createProjects locations secrets: createwrite
  • gcp_secret_manager.regional_secrets.deleteProjects locations secrets: deletedestructive
  • gcp_secret_manager.regional_secrets.enable_managed_rotationProjects locations secrets: enable managed rotationdestructive
  • gcp_secret_manager.regional_secrets.getProjects locations secrets: getread
  • gcp_secret_manager.regional_secrets.get_iam_policyProjects locations secrets: get iam policyread
  • gcp_secret_manager.regional_secrets.listProjects locations secrets: listread
  • gcp_secret_manager.regional_secrets.patchProjects locations secrets: patchwrite
  • gcp_secret_manager.regional_secrets.rotate_secretProjects locations secrets: rotate secretdestructive
  • gcp_secret_manager.regional_secrets.set_iam_policyProjects locations secrets: set iam policydestructive
  • gcp_secret_manager.regional_secrets.test_iam_permissionsProjects locations secrets: test iam permissionsread
Secrets11
  • gcp_secret_manager.secrets.add_versionProjects secrets: add versionwrite
  • gcp_secret_manager.secrets.createProjects secrets: createwrite
  • gcp_secret_manager.secrets.deleteProjects secrets: deletedestructive
  • gcp_secret_manager.secrets.enable_managed_rotationProjects secrets: enable managed rotationdestructive
  • gcp_secret_manager.secrets.getProjects secrets: getread
  • gcp_secret_manager.secrets.get_iam_policyProjects secrets: get iam policyread
  • gcp_secret_manager.secrets.listProjects secrets: listread
  • gcp_secret_manager.secrets.patchProjects secrets: patchwrite
  • gcp_secret_manager.secrets.rotate_secretProjects secrets: rotate secretdestructive
  • gcp_secret_manager.secrets.set_iam_policyProjects secrets: set iam policydestructive
  • gcp_secret_manager.secrets.test_iam_permissionsProjects secrets: test iam permissionsread
Regional secrets versions6
  • gcp_secret_manager.regional_secrets_versions.accessProjects locations secrets versions: accessread
  • gcp_secret_manager.regional_secrets_versions.destroyProjects locations secrets versions: destroydestructive
  • gcp_secret_manager.regional_secrets_versions.disableProjects locations secrets versions: disablewrite
  • gcp_secret_manager.regional_secrets_versions.enableProjects locations secrets versions: enablewrite
  • gcp_secret_manager.regional_secrets_versions.getProjects locations secrets versions: getread
  • gcp_secret_manager.regional_secrets_versions.listProjects locations secrets versions: listread
Secrets versions6
  • gcp_secret_manager.secrets_versions.accessProjects secrets versions: accessread
  • gcp_secret_manager.secrets_versions.destroyProjects secrets versions: destroydestructive
  • gcp_secret_manager.secrets_versions.disableProjects secrets versions: disablewrite
  • gcp_secret_manager.secrets_versions.enableProjects secrets versions: enablewrite
  • gcp_secret_manager.secrets_versions.getProjects secrets versions: getread
  • gcp_secret_manager.secrets_versions.listProjects secrets versions: listread
Locations2
  • gcp_secret_manager.locations.getProjects locations: getread
  • gcp_secret_manager.locations.listProjects locations: listread

Questions

The Google Secret Manager MCP server, answered.

Is there a Google Secret Manager MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 36 Google Secret Manager actions across regional secrets, secrets, regional secrets versions and secrets versions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Google Secret Manager.

What do I need to connect Google Secret Manager?

Your own Google Secret Manager OAuth app, registered with Google Secret Manager (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Google Secret Manager app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. Plus your host. The free call account { op: "connections.requirements", service: "gcp_secret_manager" } lists exactly what to paste.

Can an AI agent delete or change things in Google Secret Manager?

Only if its key allows it, and only with an explicit confirmation. 10 Google Secret Manager actions are destructive, including projects secrets: delete, projects secrets: rotate secret and projects secrets: set iam policy. 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 Google Secret Manager API limit?

actionlake paces every call to the limits in the Google Secret Manager service file: 600 calls a minute per connection. Repeated reads are answered from cache (2 Google Secret Manager actions can be), which never reaches Google Secret Manager.

What does a Google Secret Manager action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (5 Google Secret Manager actions page). Cache hits, searches, dry runs and calls Google Secret Manager 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 Google Secret Manager API does it cover?

The Google Cloud Secret Manager API v1 (secrets, versions, access, rotation, IAM, regional secrets, locations) API secretmanager v1 (Discovery revision 20260925) at secretmanager.googleapis.com by default, or the base URL set when you connect. It is built from Google Secret Manager's documentation as read on 23 October 2026. 36 actions in 5 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Google Secret Manager 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 Google Secret Manager 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.

More connectors like Google Secret Manager

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by Google Secret Manager; the name is the vendor's own. Counts are from the Google Secret Manager service file, version 1.0.0.

Give your agent Google Secret Manager today.

Connect Google Secret Manager freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.