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)

举报或申请下架