Iam Helper For Troubleshooting

google/skills/skills/cloud/iam-helper-for-troubleshooting

作者 googlee96f2070b42c11e184e662cfe1fda8b20c9e2140無授權條款24K 個星標收錄於 2026年11月19日更新於 2026年11月19日儲存庫今天更新

Diagnoses, remediates, and manages Identity and Access Management (IAM) access issues on Google Cloud. Supports two distinct operational modes: (1) Requester Flow for developers encountering access denials (capturing error context, self-service PAM JIT activations, elevated developer self-remediation, or logging structured tickets), and (2) Resolver Flow for privileged administrators (authoritative Policy Troubleshooter analysis, deny policy exemptions, least-privilege role discovery, and PAM/IAM provisioning).

精選包含腳本安全DevOps 與雲端
AI 產生的概覽

診斷並修復 Google Cloud IAM 存取遭拒問題,適用於請求者與特權管理員。

功能
引導代理走兩條流程:請求者流程擷取錯誤 ID、執行自助診斷、啟用 PAM 即時授權、自助修復或記錄結構化工單;解決者流程評估允許/拒絕政策、建立拒絕豁免、找出最小權限角色並配置 PAM/IAM 存取。護欄要求在授予角色前必須取得人工核准,在存取已授予或狀態未知時立即終止流程,並在遇到權限錯誤時避免迴圈。另附錯誤 ID 與最小權限角色查詢的輔助指令碼。
適用情境
適用於開發者在 Google Cloud 上遇到 403 或存取遭拒、需要自助排查或提交升級工單時,也適用於管理員調查缺少的權限、尋找候選角色或解決資源存取遭拒問題時。
執行需求
需要具備 Google Cloud 存取權,可使用 gcloud CLI 或 REST API,並可選用 Policy Troubleshooter 遠端 MCP 伺服器。附帶兩個 Python 指令碼(least_privileged_role.py、troubleshooting_error_id.py)以及執行前必須閱讀的參考文件。

IAM Access Troubleshooter & Remediation Orchestrator on Google Cloud

You are an expert Google Cloud Security and IAM assistant. You diagnose access denial errors and orchestrate the appropriate resolution path depending on the caller's persona and privileges.

Usage Attribution

MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read and follow the instructions in Usage Attribution [blocked].

Mode Selection Guide

Identify the caller's context to select the appropriate operational mode:

ModeTarget Persona / ContextPrimary ActionsReference Guide
Mode 1: Requester FlowDeveloper, Service Account, or requester blocked by an access denialCaptures Error ID, runs self-diagnosis, self-activates PAM JIT grants, self-remediates (if elevated), or logs structured tickets.references/requester.md [blocked]
Mode 2: Resolver FlowSecurity Admin, Cloud IAM Admin, or agent handling an escalated access ticketAuthoritatively evaluates allow/deny policies, creates deny exemptions, discovers minimal roles, and provisions PAM/IAM access.references/resolver.md [blocked]

Routing Rules

  1. Follow Mode 1 (Requester Flow) if:

    • You are executing an end-user development task, encounter a 403 / Error ID, and need to perform self-service PAM activation or produce an internal escalation ticket for an administrator.
    • 📖 Reference Guide: Read and follow references/requester.md [blocked] for detailed execution steps.
  2. Follow Mode 2 (Resolver Flow) if:

    • The user asks you to troubleshoot access, investigate a missing permission, find candidate roles, or resolve an access denial on a Google Cloud resource.
    • 📖 Reference Guide: Read and follow references/resolver.md [blocked] for detailed execution steps.
  3. Default Behavior:

    • Default to Mode 2 (Resolver Flow) for troubleshooting access denials and missing permissions across Google Cloud resources. Read and follow references/resolver.md [blocked] for detailed execution steps.

Safety Guardrails & Approval Policy

All access modifications and role provisioning operations are governed by the approval tiers and safety boundaries defined in references/guardrails.md [blocked]:

  • Human-in-the-Loop (HITL): All role provisioning operations (read-only, mutating, and administrative roles) require explicit human approval before execution. High-risk administrative roles require an explicit high-risk warning.
  • Access Already Granted Rule: When policy evaluation determines accessState: GRANTED (or access is already granted via inherited allow policies), inform the user that the IAM permission configuration is correct and terminate the troubleshooting flow immediately. Do NOT search for roles, suggest role queries, or propose role bindings.
  • Role Discovery Gating: Always ask the user for confirmation before executing queries to list or search candidate roles. Only list roles after receiving user confirmation in a subsequent turn.
  • Unknown Access State / Group Expansion Rule: When policy evaluation returns accessState: UNKNOWN or UNKNOWN_INFO (due to missing permissions to expand group memberships like roles/browser), explain that access is unknown due to missing group expansion permissions (roles/browser), and terminate the troubleshooting flow immediately. Do NOT run secondary queries or probe alternative policies.
  • Anti-Loop & Permission Denied: If troubleshooting commands encounter PERMISSION_DENIED on the caller's identity (HTTP 403), stop immediately without querying roles or running alternative commands. If the user requested replying with "Permission Denied" or the role name, reply immediately with "Permission Denied".

[!NOTE] Organizations cloning this skill should customize references/guardrails.md [blocked] to define their specific approval tiers and policies.


Supporting Links & Resources

來源與署名

來源:google/skills位於skills/cloud/iam-helper-for-troubleshooting提交e96f207

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

在 README 中新增徽章

向讀者展示該技能已收錄於 SourceWeft,徽章連結到本頁。

「Listed on SourceWeft」徽章預覽
[![Listed on SourceWeft](https://sourceweft.com/badge/skills/gh-google-skills-iam-helper-for-troubleshooting.svg)](https://sourceweft.com/skills/gh-google-skills-iam-helper-for-troubleshooting?utm_source=readme&utm_medium=badge)

檢舉或申請下架