Skip to content

Connectors · Identity & security

Google Security Command Center MCP server for AI agents.

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

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_security_command_center.folders_locations_mute_configs.get",  intent: "check which Google Security Command Center account is connected"}# Folders locations mute configs: get · read · 1 upstream call
  • 324actionsin one signed file
  • 150readlook, never change
  • 135writecreate and update
  • 39wait for a yesdestructive, confirmed first

Set up

Connect Google Security Command Center 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 Security Command Center.

    OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Security Command Center, 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 Security Command Center needs an OAuth app of your own, registered in its developer portal. actionlake has no Google Security Command Center 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 Security Command Center API…
    • client_secretGoogle OAuth client secret
    account { op: "connections.requirements", service: "gcp_security_command_center" }
    # 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_security_command_center.folders_locations_mute_configs.get" }# folders locations mute configs: get · read · 1 upstream callcheck { action: "gcp_security_command_center.folders_mute_configs.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Google Security Command Center at a glance

Sign-in
OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Security Command Center, 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
Limits we pace to
600 calls a minute, per connection
API covered
Google Security Command Center (findings, sources, assets, mute rules, notifications, exports, custom modules, attack paths) API securitycenter v1 + v2 (Discovery revision 20261005)securitycenter.googleapis.com
Built from
Google Security Command Center's documentation, read 23 October 2026securitycenter.googleapis.comsecuritycenter.googleapis.comcloud.google.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
146 of 150 reads, for up to 5 minutes; a write clears what it affects
Shared entities
3, so ask can line Google Security Command Center 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 Security Command Center.

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

  • 150readlook, never change
  • 135writecreate and update
  • 39destructivewait for a confirmation
  1. V2 organizations sources locations findings

    8

    2 read · 6 write · 0 destructive

    Organizations sources locations findings: list · Organizations sources locations findings: create · Organizations sources locations findings: patch · Organizations sources locations findings: export

  2. Folders security health analytics settings custom modules

    7

    4 read · 2 write · 1 destructive

    Folders security health analytics settings custom modules: list · Folders security health analytics settings custom modules: create · Folders security health analytics settings custom modules: get · Folders security health analytics settings custom modules: patch

  3. Organizations security health analytics settings custom modules

    7

    4 read · 2 write · 1 destructive

    Organizations security health analytics settings custom modules: list · Organizations security health analytics settings custom modules: create · Organizations security health analytics settings custom modules: get · Organizations security health analytics settings custom modules: patch

  4. Organizations sources

    7

    4 read · 2 write · 1 destructive

    Organizations sources: create · Organizations sources: list · Organizations sources: test iam permissions · Organizations sources: get

  5. Organizations sources findings

    7

    2 read · 5 write · 0 destructive

    Organizations sources findings: list · Organizations sources findings: create · Organizations sources findings: patch · Organizations sources findings: group

  6. Projects security health analytics settings custom modules

    7

    4 read · 2 write · 1 destructive

    Projects security health analytics settings custom modules: list · Projects security health analytics settings custom modules: create · Projects security health analytics settings custom modules: get · Projects security health analytics settings custom modules: patch

  7. V2 folders sources locations findings

    7

    2 read · 5 write · 0 destructive

    Folders sources locations findings: list · Folders sources locations findings: patch · Folders sources locations findings: export · Folders sources locations findings: group

  8. V2 organizations sources

    7

    4 read · 2 write · 1 destructive

    Organizations sources: create · Organizations sources: list · Organizations sources: test iam permissions · Organizations sources: get

96 more areas · 267 actions
  • V2 organizations sources findings 7
  • V2 projects sources locations findings 7
  • Folders event threat detection settings custom modules 6
  • Folders sources findings 6
  • Organizations event threat detection settings custom modules 6
  • Projects event threat detection settings custom modules 6
  • Projects sources findings 6
  • V2 folders sources findings 6
  • V2 projects sources findings 6
  • Folders big query exports 5
  • Folders mute configs 5
  • Folders notification configs 5
  • Organizations big query exports 5
  • Organizations mute configs 5
  • Organizations notification configs 5
  • Organizations resource value configs 5
  • Projects big query exports 5
  • Projects mute configs 5
  • Projects notification configs 5
  • V2 folders locations big query exports 5
  • V2 folders locations mute configs 5
  • V2 folders locations notification configs 5
  • V2 folders mute configs 5
  • V2 organizations locations big query exports 5
  • V2 organizations locations mute configs 5
  • V2 organizations locations notification configs 5
  • V2 organizations locations resource value configs 5
  • V2 organizations mute configs 5
  • V2 organizations resource value configs 5
  • V2 projects locations big query exports 5
  • V2 projects locations mute configs 5
  • V2 projects locations notification configs 5
  • V2 projects mute configs 5
  • Organizations assets 4
  • Organizations operations 4
  • V2 organizations operations 4
  • Folders assets 3
  • Folders locations mute configs 3
  • Organizations locations mute configs 3
  • Projects assets 3
  • Projects locations mute configs 3
  • Folders event threat detection settings effective custom modules 2
  • Folders security health analytics settings effective custom modules 2
  • Organizations 2
  • Organizations event threat detection settings effective custom modules 2
  • Organizations security health analytics settings effective custom modules 2
  • Organizations simulations valued resources 2
  • Projects event threat detection settings effective custom modules 2
  • Projects security health analytics settings effective custom modules 2
  • V2 organizations simulations valued resources 2
  • Folders event threat detection settings 1
  • Folders findings 1
  • Folders sources 1
  • Folders sources findings external systems 1
  • Organizations attack paths 1
  • Organizations event threat detection settings 1
  • Organizations findings 1
  • Organizations simulations 1
  • Organizations simulations attack exposure results attack paths 1
  • Organizations simulations attack exposure results valued resources 1
  • Organizations simulations attack paths 1
  • Organizations simulations valued resources attack paths 1
  • Organizations sources findings external systems 1
  • Organizations valued resources 1
  • Projects event threat detection settings 1
  • Projects findings 1
  • Projects sources 1
  • Projects sources findings external systems 1
  • V2 folders assets 1
  • V2 folders findings 1
  • V2 folders locations findings 1
  • V2 folders sources 1
  • V2 folders sources findings external systems 1
  • V2 folders sources locations findings external systems 1
  • V2 organizations assets 1
  • V2 organizations attack paths 1
  • V2 organizations findings 1
  • V2 organizations locations findings 1
  • V2 organizations locations simulations 1
  • V2 organizations locations simulations attack exposure results attack paths 1
  • V2 organizations locations simulations valued resources 1
  • V2 organizations locations simulations valued resources attack paths 1
  • V2 organizations simulations 1
  • V2 organizations simulations attack exposure results attack paths 1
  • V2 organizations simulations attack exposure results valued resources 1
  • V2 organizations simulations attack paths 1
  • V2 organizations simulations valued resources attack paths 1
  • V2 organizations sources findings external systems 1
  • V2 organizations sources locations findings external systems 1
  • V2 organizations valued resources 1
  • V2 projects assets 1
  • V2 projects findings 1
  • V2 projects locations findings 1
  • V2 projects sources 1
  • V2 projects sources findings external systems 1
  • V2 projects sources locations findings external systems 1

Top actions

The Google Security Command Center API, shaped for agents.

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

ActionWhat it doesEffectSame name in
gcp_security_command_center.organizations_assets.listOrganizations assets: listList assets under an organization.readasset.asset.list42 connectors
gcp_security_command_center.folders_assets.listFolders assets: listList assets under a folder.readasset.asset.list42 connectors
gcp_security_command_center.organizations_sources_findings.listOrganizations sources findings: listList findings under a source of an organization.readsecurity.alert.list22 connectors
gcp_security_command_center.organizations_mute_configs.listOrganizations mute configs: listList mute configs under an organization.readsecurity.filter_rule.list4 connectors
gcp_security_command_center.folders_sources_findings.listFolders sources findings: listList findings under a source of a folder.readsecurity.alert.list22 connectors
gcp_security_command_center.folders_mute_configs.listFolders mute configs: listList mute configs under a folder.readsecurity.filter_rule.list4 connectors
gcp_security_command_center.folders_mute_configs.createFolders mute configs: createCreate a mute config under a folder.writesecurity.filter_rule.create4 connectors
gcp_security_command_center.projects_mute_configs.createProjects mute configs: createCreate a mute config under a project.writesecurity.filter_rule.create4 connectors
gcp_security_command_center.organizations_mute_configs.createOrganizations mute configs: createCreate a mute config under an organization.writesecurity.filter_rule.create4 connectors
gcp_security_command_center.folders_event_threat_detection_settings_custom_modules.listFolders event threat detection settings custom modules: listList custom modules under Event Threat Detection settings of a folder.readsecurity.detection_rule.list13 connectors
gcp_security_command_center.projects_event_threat_detection_settings_custom_modules.listProjects event threat detection settings custom modules: listList custom modules under Event Threat Detection settings of a project.readsecurity.detection_rule.list13 connectors
gcp_security_command_center.folders_mute_configs.deleteFolders mute configs: deleteDelete a mute config.destructivesecurity.filter_rule.delete4 connectors

Try it

Prompts to paste into Claude.

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

  1. Readread

    Which Google Security Command Center alerts are open right now? Group them by service.

    callsgcp_security_command_center.organizations_sources_findings.list

  2. Writewrite

    Folders mute configs: create in Google Security Command Center. Show me exactly what you will send before you save it.

    callsgcp_security_command_center.folders_mute_configs.create

Governance for Google Security Command Center

Destructive actions wait for a yes.

39 Google Security Command Center actions are destructive. The first 10:

  • Folders mute configs: deletegcp_security_command_center.folders_mute_configs.delete
  • Projects mute configs: deletegcp_security_command_center.projects_mute_configs.delete
  • Organizations mute configs: deletegcp_security_command_center.organizations_mute_configs.delete
  • Folders locations mute configs: deletegcp_security_command_center.folders_locations_mute_configs.delete
  • Projects locations mute configs: deletegcp_security_command_center.projects_locations_mute_configs.delete
  • Organizations locations mute configs: deletegcp_security_command_center.organizations_locations_mute_configs.delete
  • Folders event threat detection settings custom modules: deletegcp_security_command_center.folders_event_threat_detection_settings_custom_modules.delete
  • Projects event threat detection settings custom modules: deletegcp_security_command_center.projects_event_threat_detection_settings_custom_modules.delete
  • Folders security health analytics settings custom modules: deletegcp_security_command_center.folders_security_health_analytics_settings_custom_modules.delete
  • Projects security health analytics settings custom modules: deletegcp_security_command_center.projects_security_health_analytics_settings_custom_modules.delete

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_security_command_center.folders_mute_configs.deleteconfirm_policy: human

Folders mute configs: delete?

intent: the user asked me to folders mute configs: delete

run suspended · waiting for a named person · key gcp-security-command-center-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "gcp-security-command-center-agent",  allowed_actions: ["gcp_security_command_center.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "gcp_security_command_center.folders_mute_configs.delete", approver: "[email protected]" },    { match: "gcp_security_command_center.projects_mute_configs.delete", approver: "[email protected]" },    { match: "gcp_security_command_center.organizations_mute_configs.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Google Security Command Center only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Google Security Command Center costs on actionlake.

Every Google Security Command Center action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Google Security Command Center 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 324 Google Security Command Center actions
  • 90actions pageeach page of a long list is one call
  • 146reads 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 Security Command Center action.

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

V2 organizations sources locations findings8
  • gcp_security_command_center.v2_organizations_sources_locations_findings.createOrganizations sources locations findings: createwrite
  • gcp_security_command_center.v2_organizations_sources_locations_findings.exportOrganizations sources locations findings: exportwrite
  • and 6 more in this area
Folders security health analytics settings custom modules7
  • gcp_security_command_center.folders_security_health_analytics_settings_custom_modules.createFolders security health analytics settings custom modules: createwrite
  • gcp_security_command_center.folders_security_health_analytics_settings_custom_modules.getFolders security health analytics settings custom modules: getread
  • and 5 more in this area
Organizations security health analytics settings custom modules7
  • gcp_security_command_center.organizations_security_health_analytics_settings_custom_modules.createOrganizations security health analytics settings custom modules: createwrite
  • gcp_security_command_center.organizations_security_health_analytics_settings_custom_modules.getOrganizations security health analytics settings custom modules: getread
  • and 5 more in this area
Organizations sources7
  • gcp_security_command_center.organizations_sources.createOrganizations sources: createwrite
  • gcp_security_command_center.organizations_sources.getOrganizations sources: getread
  • and 5 more in this area
Organizations sources findings7
  • gcp_security_command_center.organizations_sources_findings.createOrganizations sources findings: createwrite
  • gcp_security_command_center.organizations_sources_findings.groupOrganizations sources findings: groupread
  • and 5 more in this area
Projects security health analytics settings custom modules7
  • gcp_security_command_center.projects_security_health_analytics_settings_custom_modules.createProjects security health analytics settings custom modules: createwrite
  • gcp_security_command_center.projects_security_health_analytics_settings_custom_modules.getProjects security health analytics settings custom modules: getread
  • and 5 more in this area
V2 folders sources locations findings7
  • gcp_security_command_center.v2_folders_sources_locations_findings.exportFolders sources locations findings: exportwrite
  • gcp_security_command_center.v2_folders_sources_locations_findings.groupFolders sources locations findings: groupread
  • and 5 more in this area
V2 organizations sources7
  • gcp_security_command_center.v2_organizations_sources.createOrganizations sources: createwrite
  • gcp_security_command_center.v2_organizations_sources.getOrganizations sources: getread
  • and 5 more in this area
V2 organizations sources findings7
  • gcp_security_command_center.v2_organizations_sources_findings.createOrganizations sources findings: createwrite
  • gcp_security_command_center.v2_organizations_sources_findings.groupOrganizations sources findings: groupread
  • and 5 more in this area
V2 projects sources locations findings7
  • gcp_security_command_center.v2_projects_sources_locations_findings.exportProjects sources locations findings: exportwrite
  • gcp_security_command_center.v2_projects_sources_locations_findings.groupProjects sources locations findings: groupread
  • and 5 more in this area
Folders event threat detection settings custom modules6
  • gcp_security_command_center.folders_event_threat_detection_settings_custom_modules.createFolders event threat detection settings custom modules: createwrite
  • gcp_security_command_center.folders_event_threat_detection_settings_custom_modules.getFolders event threat detection settings custom modules: getread
  • and 4 more in this area
Folders sources findings6
  • gcp_security_command_center.folders_sources_findings.groupFolders sources findings: groupread
  • gcp_security_command_center.folders_sources_findings.listFolders sources findings: listread
  • and 4 more in this area
Organizations event threat detection settings custom modules6
  • gcp_security_command_center.organizations_event_threat_detection_settings_custom_modules.createOrganizations event threat detection settings custom modules: createwrite
  • gcp_security_command_center.organizations_event_threat_detection_settings_custom_modules.getOrganizations event threat detection settings custom modules: getread
  • and 4 more in this area
Projects event threat detection settings custom modules6
  • gcp_security_command_center.projects_event_threat_detection_settings_custom_modules.createProjects event threat detection settings custom modules: createwrite
  • gcp_security_command_center.projects_event_threat_detection_settings_custom_modules.getProjects event threat detection settings custom modules: getread
  • and 4 more in this area
Projects sources findings6
  • gcp_security_command_center.projects_sources_findings.groupProjects sources findings: groupread
  • gcp_security_command_center.projects_sources_findings.listProjects sources findings: listread
  • and 4 more in this area
V2 folders sources findings6
  • gcp_security_command_center.v2_folders_sources_findings.groupFolders sources findings: groupread
  • gcp_security_command_center.v2_folders_sources_findings.listFolders sources findings: listread
  • and 4 more in this area
V2 projects sources findings6
  • gcp_security_command_center.v2_projects_sources_findings.groupProjects sources findings: groupread
  • gcp_security_command_center.v2_projects_sources_findings.listProjects sources findings: listread
  • and 4 more in this area
Folders big query exports5
  • gcp_security_command_center.folders_big_query_exports.createFolders big query exports: createwrite
  • gcp_security_command_center.folders_big_query_exports.deleteFolders big query exports: deletedestructive
  • and 3 more in this area
Folders mute configs5
  • gcp_security_command_center.folders_mute_configs.createFolders mute configs: createwrite
  • gcp_security_command_center.folders_mute_configs.deleteFolders mute configs: deletedestructive
  • and 3 more in this area
Folders notification configs5
  • gcp_security_command_center.folders_notification_configs.createFolders notification configs: createwrite
  • gcp_security_command_center.folders_notification_configs.deleteFolders notification configs: deletedestructive
  • and 3 more in this area
Organizations big query exports5
  • gcp_security_command_center.organizations_big_query_exports.createOrganizations big query exports: createwrite
  • gcp_security_command_center.organizations_big_query_exports.deleteOrganizations big query exports: deletedestructive
  • and 3 more in this area
Organizations mute configs5
  • gcp_security_command_center.organizations_mute_configs.createOrganizations mute configs: createwrite
  • gcp_security_command_center.organizations_mute_configs.deleteOrganizations mute configs: deletedestructive
  • and 3 more in this area
Organizations notification configs5
  • gcp_security_command_center.organizations_notification_configs.createOrganizations notification configs: createwrite
  • gcp_security_command_center.organizations_notification_configs.deleteOrganizations notification configs: deletedestructive
  • and 3 more in this area
Organizations resource value configs5
  • gcp_security_command_center.organizations_resource_value_configs.batch_createOrganizations resource value configs: batch createwrite
  • gcp_security_command_center.organizations_resource_value_configs.deleteOrganizations resource value configs: deletedestructive
  • and 3 more in this area
Projects big query exports5
  • gcp_security_command_center.projects_big_query_exports.createProjects big query exports: createwrite
  • gcp_security_command_center.projects_big_query_exports.deleteProjects big query exports: deletedestructive
  • and 3 more in this area
Projects mute configs5
  • gcp_security_command_center.projects_mute_configs.createProjects mute configs: createwrite
  • gcp_security_command_center.projects_mute_configs.deleteProjects mute configs: deletedestructive
  • and 3 more in this area
Projects notification configs5
  • gcp_security_command_center.projects_notification_configs.createProjects notification configs: createwrite
  • gcp_security_command_center.projects_notification_configs.deleteProjects notification configs: deletedestructive
  • and 3 more in this area
V2 folders locations big query exports5
  • gcp_security_command_center.v2_folders_locations_big_query_exports.createFolders locations big query exports: createwrite
  • gcp_security_command_center.v2_folders_locations_big_query_exports.deleteFolders locations big query exports: deletedestructive
  • and 3 more in this area
V2 folders locations mute configs5
  • gcp_security_command_center.v2_folders_locations_mute_configs.createFolders locations mute configs: createwrite
  • gcp_security_command_center.v2_folders_locations_mute_configs.deleteFolders locations mute configs: deletedestructive
  • and 3 more in this area
V2 folders locations notification configs5
  • gcp_security_command_center.v2_folders_locations_notification_configs.createFolders locations notification configs: createwrite
  • gcp_security_command_center.v2_folders_locations_notification_configs.deleteFolders locations notification configs: deletedestructive
  • and 3 more in this area

V2 folders mute configs 5V2 organizations locations big query exports 5V2 organizations locations mute configs 5V2 organizations locations notification configs 5V2 organizations locations resource value configs 5V2 organizations mute configs 5V2 organizations resource value configs 5V2 projects locations big query exports 5V2 projects locations mute configs 5V2 projects locations notification configs 5V2 projects mute configs 5Organizations assets 4Organizations operations 4V2 organizations operations 4Folders assets 3Folders locations mute configs 3Organizations locations mute configs 3Projects assets 3Projects locations mute configs 3Folders event threat detection settings effective custom modules 2Folders security health analytics settings effective custom modules 2Organizations 2Organizations event threat detection settings effective custom modules 2Organizations security health analytics settings effective custom modules 2Organizations simulations valued resources 2Projects event threat detection settings effective custom modules 2Projects security health analytics settings effective custom modules 2V2 organizations simulations valued resources 2Folders event threat detection settings 1Folders findings 1Folders sources 1Folders sources findings external systems 1Organizations attack paths 1Organizations event threat detection settings 1Organizations findings 1Organizations simulations 1Organizations simulations attack exposure results attack paths 1Organizations simulations attack exposure results valued resources 1Organizations simulations attack paths 1Organizations simulations valued resources attack paths 1Organizations sources findings external systems 1Organizations valued resources 1Projects event threat detection settings 1Projects findings 1Projects sources 1Projects sources findings external systems 1V2 folders assets 1V2 folders findings 1V2 folders locations findings 1V2 folders sources 1V2 folders sources findings external systems 1V2 folders sources locations findings external systems 1V2 organizations assets 1V2 organizations attack paths 1V2 organizations findings 1V2 organizations locations findings 1V2 organizations locations simulations 1V2 organizations locations simulations attack exposure results attack paths 1V2 organizations locations simulations valued resources 1V2 organizations locations simulations valued resources attack paths 1V2 organizations simulations 1V2 organizations simulations attack exposure results attack paths 1V2 organizations simulations attack exposure results valued resources 1V2 organizations simulations attack paths 1V2 organizations simulations valued resources attack paths 1V2 organizations sources findings external systems 1V2 organizations sources locations findings external systems 1V2 organizations valued resources 1V2 projects assets 1V2 projects findings 1V2 projects locations findings 1V2 projects sources 1V2 projects sources findings external systems 1V2 projects sources locations findings external systems 1

This index shows a sample of each area. All 324 actions, with their inputs and prices, are in the catalogue, which a free sandbox key can search.

Questions

The Google Security Command Center MCP server, answered.

Is there a Google Security Command Center MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 324 Google Security Command Center actions across v2 organizations sources locations findings, folders security health analytics settings custom modules, organizations security health analytics settings custom modules and organizations sources, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Google Security Command Center.

What do I need to connect Google Security Command Center?

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

Can an AI agent delete or change things in Google Security Command Center?

Only if its key allows it, and only with an explicit confirmation. 39 Google Security Command Center actions are destructive, including folders mute configs: delete, projects mute configs: delete and organizations mute configs: delete. 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 Security Command Center API limit?

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

What does a Google Security Command Center action cost?

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

The Google Security Command Center (findings, sources, assets, mute rules, notifications, exports, custom modules, attack paths) API securitycenter v1 + v2 (Discovery revision 20261005) at securitycenter.googleapis.com. It is built from Google Security Command Center's documentation as read on 23 October 2026. 324 actions in 104 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Google Security Command Center 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 Security Command Center 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 Google Security Command Center today.

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