Google Cloud Scc Query
GoogleOfficialPublished by Google
- Skill
- Tool integration
- Security
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured, read-only approach to querying Google Cloud Security Command Center (SCC). It enables users to retrieve detailed information about security findings, including vulnerabilities, threats, toxic combinations, and external exposures. The skill enforces strict safety protocols, requiring explicit parent resource scopes and prohibiting any configuration changes or remediation actions. It supports both global and regional data residency configurations, ensuring accurate data retrieval across different Google Cloud environments.
What it does
- Retrieves detailed JSON payloads for specific security findings by name.
- Lists active findings filtered by class, state, or category.
- Provides grouping functionality for high-level security landscape summaries.
- Supports regional endpoint overrides for data residency compliance.
- Analyzes finding payloads to extract critical risk indicators like CVSS scores or attack exposure.
- Enforces read-only execution to prevent accidental configuration changes.
When to use it
- When you need to perform triage on a specific security finding identified in SCC.
- When you need to list active vulnerabilities or threats within a specific project, folder, or organization.
- When you need to generate a summary report of security findings grouped by category or resource.
- When you are investigating a potential toxic combination or external exposure risk.
Advantages
- Ensures safe, read-only interaction with sensitive security data.
- Standardizes query patterns to avoid common CLI errors.
- Provides clear guidance on handling regional data residency requirements.
- Facilitates structured analysis of complex finding payloads.
- Prevents accidental remediation or configuration changes.
Usage examples
- “List all active vulnerabilities in project my-project-123.”
- The agent executes a filtered gcloud scc findings list command to return a list of active vulnerabilities, including their severity and category.
- “Get full details for the finding named organizations/123/sources/456/findings/789.”
- The agent retrieves the complete JSON payload for the specified finding, allowing for a deep dive into its attributes.
- “Show me a summary of active findings grouped by category for organization 987.”
- The agent executes a gcloud scc findings group command to provide a count of active findings categorized by their type.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/google/google-cloud-scc-query/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip google-cloud-scc-query.zip -d .agents/skills
Documentation by Google
Security Command Center Query Skill on Google Cloud
Provides guidelines and read-only gcloud CLI command patterns for querying and
retrieving security findings, external exposures, toxic combinations,
vulnerabilities, threats, and sensitive data risks from Security Command Center
on Google Cloud.
[!IMPORTANT] There is NO
gcloud scc findings describecommand (Invalid choice: 'describe'). To retrieve details for a specific finding by its name, always usegcloud scc findings listwith a filter onname.
Usage Attribution
MUST READ: Before executing any gcloud, REST API, or MCP command, you
MUST read and follow the instructions in
Usage Attribution.
Core Execution Rules
Read-Only & Zero-Speculation (Parent Scope Required): Keep all executions strictly read-only. Every
gcloud scc findings listorgroupcommand strictly requires an explicit{parent}scope (organizations/{id},projects/{id}, orfolders/{id}). If the parent scope is missing from the prompt and cannot be inferred from a full finding name, DO NOT run anygcloudcommands (do not execute queries without parent, and never inspectgcloud config). Halt immediately before executing commands and ask the user for the parent resource scope.Bounded Execution & No Runaway Loops:
Limit tool calls to what is strictly necessary to complete the query (typically 1 call for direct queries, or 2 calls for List → Deep Dive workflows).
If a command fails due to permission/auth errors, or if a specific finding query returns
[], halt immediately. Do not attempt blind brute-force retries with different flags, and never search the local workspace for credentials.
Immediate Halt on Errors: If any command fails with
PERMISSION_DENIED,IAM_PERMISSION_DENIED, credential expiration, or network timeouts, halt immediately and report the verbatim error message. Do not search the workspace for credentials or run diagnostic loops.Ambiguous or Multiple Findings: If multiple finding names are provided when a single finding report is requested, or if listing returns multiple findings, do not investigate all of them or unilaterally pick one. Halt immediately without running queries and ask the user to clarify which specific finding name they want details for. If zero findings are returned from a query, report that no active findings exist and halt immediately.
Do Not Query Attack Path Resources: Analyze only the data present in the Security Command Center finding JSON payload. Do not run commands to describe, verify, or query underlying Google Cloud resources (such as VMs, Cloud Storage buckets, service accounts, or IAM policies).
Parent Scope Resolution:
For listing and grouping, format the parent resource path as
organizations/{org_id},projects/{project_id}, orfolders/{folder_id}.For deep dive queries on a specific finding name, extract the
{parent}resource prefix before/sources/...:organizations/{org_id}/sources/...→{parent}isorganizations/{org_id}folders/{folder_id}/sources/...→{parent}isfolders/{folder_id}projects/{project_id}/sources/...→{parent}isprojects/{project_id}Extract the parent prefix regardless of whether the finding resource name is global (4-segment) or location-qualified (5-segment with/locations/{location}/). Execute the deep dive query using the extracted{parent}. Do not reject or halt on project- or folder-level findings.
Data Residency & Regional Endpoints
When Data Residency (DRZ) is enabled, findings are stored and accessible only
within their designated regional location (us, eu, or me-central2).
Queries across different locations do not return findings from other regions.
1. Location Parameterization
All gcloud scc findings commands require specifying the target location via
--location={location}:
Default:
global(used when data residency is not enabled or for global findings).Supported Regional Locations:
us(United States multi-region)eu(European Union multi-region)me-central2(Kingdom of Saudi Arabia regional location)
2. API Endpoint Overrides
When data residency (DRZ) is enabled for an organization in a regional location
(us, eu, or me-central2), configure the regional API endpoint override
before executing finding queries:
gcloud config set api_endpoint_overrides/securitycenter https://securitycenter.{LOCATION}.rep.googleapis.com/Example for the European Union (eu) region:
gcloud config set api_endpoint_overrides/securitycenter https://securitycenter.eu.rep.googleapis.com/To reset the endpoint back to default global routing:
gcloud config unset api_endpoint_overrides/securitycenter3. Location-Qualified Finding Resource Names
Regional finding resource names include the /locations/{location}/ path
segment:
Organization-level:
organizations/{org_id}/sources/{source_id}/locations/{location}/findings/{finding_id}Folder-level:
folders/{folder_id}/sources/{source_id}/locations/{location}/findings/{finding_id}Project-level:
projects/{project_id}/sources/{source_id}/locations/{location}/findings/{finding_id}
When performing a Deep Dive on a location-qualified finding name:
Extract the
{parent}scope (the prefix before/sources/..., e.g.,organizations/{org_id}).Extract the
{location}from/locations/{location}/(e.g.,eu,us,me-central2). If not present in the finding name, default toglobal(or the user-specified location).Execute the query with
--location={location}and--filter="name=\"{finding_name}\"".
Intent-Based Query Strategies
1. Deep Dive (Specific Finding Details)
Intent: User provides a specific finding name or explicitly asks to retrieve
all details for one finding.
Action: Execute gcloud scc findings list with a strict filter on name
and NO --field-mask to retrieve the complete JSON payload. Specify
--location={location} (default global unless a regional location is
indicated or present in the finding name).
gcloud scc findings list {parent} \
--location={location} \
--filter="name=\"{finding_name}\"" \
--format="json" --limit=12. Listing (Filtered Projection)
Intent: User wants to list active findings matching criteria without pulling
full nested payloads.
Action: Use --field-mask projection to restrict output size. Specify
--location={location} (default global unless querying a specific region).
gcloud scc findings list {parent} \
--location={location} \
--filter="{filter_expression}" \
--field-mask="finding.name,finding.parentDisplayName,finding.findingClass,finding.category,finding.state,finding.eventTime,finding.severity,finding.resourceName" \
--format="json" --order-by="severity,event_time desc" --limit=100| Intent / Target Finding Class | --filter Expression |
|---|---|
| All Active Findings | state="ACTIVE" |
| Vulnerabilities | `state="ACTIVE" AND |
| : : findingClass="VULNERABILITY"` : | |
| Misconfigurations | `state="ACTIVE" AND |
| : : findingClass="MISCONFIGURATION"` : | |
| Toxic Combinations | `state="ACTIVE" AND |
| : : findingClass="TOXIC_COMBINATION"` : | |
| External Exposures | `state="ACTIVE" AND |
| : : findingClass="EXTERNAL_EXPOSURE"` : | |
| Threats | state="ACTIVE" AND findingClass="THREAT" |
| Observations | `state="ACTIVE" AND |
| : : findingClass="OBSERVATION"` : | |
| Sensitive Data Risks | `state="ACTIVE" AND |
| : : findingClass="SENSITIVE_DATA_RISK"` : | |
| Chokepoints | `state="ACTIVE" AND |
| : : findingClass="CHOKEPOINT"` : | |
| Posture Violations | `state="ACTIVE" AND |
| : : findingClass="POSTURE_VIOLATION"` : | |
| Secrets | state="ACTIVE" AND findingClass="SECRET" |
| SCC Errors | `state="ACTIVE" AND |
| : : findingClass="SCC_ERROR"` : | |
| Specific Category | state="ACTIVE" AND category="{category}" |
3. Discovery & Aggregation (Grouping)
Intent: User wants high-level counts or landscape overview (e.g., "What are
the most common findings?", "Show me a summary by category").
Action: Use gcloud scc findings group. Specify --location={location}
(default global unless querying a specific region). Allowed fields for
--group-by are strictly: resource_name, category, state, parent.
gcloud scc findings group {parent} \
--location={location} \
--group-by="{group_by_field}" \
--filter="state=\"ACTIVE\"" \
--format="json"Payload Analysis & Handoff
Once the finding JSON payload is retrieved:
For
TOXIC_COMBINATIONFindings:Verify the
attackExposurefield is present and has ascore > 0.Inspect the attack path nodes, edges, or referenced
attackExposureResultto identify exposed resources and attack trajectories.
For
VULNERABILITYFindings:Extract CVSS scores, exploit signals (
exploitationActivity,observedInTheWild,zeroDay), upstream fix status (upstreamFixAvailable), and affected package details from thevulnerabilityobject to evaluate risk:vulnerability.cve.idvulnerability.cve.cvssv3.baseScorevulnerability.cve.cvssv3.attackVectorvulnerability.cve.exploitationActivityvulnerability.cve.observedInTheWildvulnerability.cve.zeroDayvulnerability.cve.upstreamFixAvailablevulnerability.offendingPackage.packageNamevulnerability.offendingPackage.packageVersionvulnerability.fixedPackage.packageVersionvulnerability.securityBulletin.suggestedUpgradeVersion
Handoff: Do not draft remediation plans, patch resources, or execute configuration commands. Pass the extracted finding payload to the appropriate remediation or IAM analyzer skill to manage the remediation action loop.
Reference Schema
See finding_schema.md for the JSON structure of a Security Command Center finding.
Files
- ATTRIBUTION.mdAdded by AutoGineer862 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md12.1 KiB
- references/attribution.md1.9 KiB
- references/finding_schema.md3.8 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs a command-line tool
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Publisher
- Google (Official)
- Source
- google/skills · skills/cloud/google-cloud-scc-query · commit 2194d3b
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Google.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download google-cloud-scc-query.zip