Skip to main content
Agent skill

Iam Helper For Policy Simulator

Safely simulates and applies Identity and Access Management (IAM) v1 (Allow) policy changes on Google Cloud. Uses the Policy Simulator to replay historical access logs against proposed policies to prevent breaking active workloads before applying the changes. Use when simulating or applying IAM v1 allow policies across Projects, Folders, or Organizations. Don't use for analyzing IAM v2 deny policies, VPC Service Controls, or performing general policy troubleshooting.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Iam Helper For Policy Simulator when an AI agent needs a reusable SKILL.md workflow for this job: Safely simulates and applies Identity and Access Management (IAM) v1 (Allow) policy changes on Google Cloud. Uses the Policy Simulator to replay historical access logs against proposed policies to prevent breaking active workloads before applying the changes. Use when simulating or applying IAM v1 allow policies across Projects, Folders, or Organizations. Don't use for analyzing IAM v2 deny policies, VPC Service Controls, or performing general policy troubleshooting.

When not to use it

Skip Iam Helper For Policy Simulator when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/iam-helper-for-policy-simulator
# Save SKILL.md to ~/.claude/skills/iam-helper-for-policy-simulator/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/iam-helper-for-policy-simulator/SKILL.md. For a shared project, commit the folder at .claude/skills/iam-helper-for-policy-simulator/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Iam Helper For Policy Simulator skill for this task: Use Iam Helper For Policy Simulator when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# IAM Policy Simulator (v1 Allow)

You are an advanced security assistant helping users safely modify IAM policies. You must NEVER apply a modifying policy change without first running a Policy Simulation to ensure existing workloads are not disrupted. You must only use standard public gcloud commands.

## Usage Attribution

**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you MUST read and follow the instructions in [Usage Attribution](references/attribution.md).

## Core Concepts & Prerequisites

* **IAM v1 (Allow Policies)**: Specifies who has access (a role) to a resource. * **Policy Simulator**: Replays the last 90 days of access logs against a proposed policy to verify if any historical access would be blocked by the change. * **Required Permissions**: The execution environment must have `roles/policysimulator.admin`, `roles/cloudasset.viewer`, and the appropriate IAM Admin roles for the target resource. * **Resource Scope**: Changes can target Projects, Folders, or Organizations.

## Execution Workflow: Plan, Simulate, Analyze, Apply

### Step 1: Retrieve Current Policy (Plan)

Fetch the baseline IAM v1 policy for the target resource (Project, Folder, or Organization) and save it to the `/tmp/` directory:

**For Projects:**

```bash gcloud projects get-iam-policy TARGET_PROJECT_ID --format=json > /tmp/current_policy.json ```

**For Folders:**

```bash gcloud resource-manager folders get-iam-policy TARGET_FOLDER_ID --format=json > /tmp/current_policy.json ```

**For Organizations:**

```bash gcloud organizations get-iam-policy TARGET_ORG_ID --format=json > /tmp/current_policy.json ```

**CRUCIAL SAFETY GATE:** Verify that the policy was successfully retrieved. If the command fails or the resulting JSON is empty, you MUST terminate the workflow immediately and inform the user. Do not proceed to prepare or simulate an empty or partial policy.

### Step 2: Prepare Proposed Policy

Create a `/tmp/proposed_policy.json` file. Modify `/tmp/current_policy.json` by adding or removing role bindings in the `bindings` array to match the requested change.

**CRUCIAL NO-OP CHECK:** Compare the proposed policy to the current policy. If no changes were actually made (e.g., you are trying to remove a role the user doesn't hold, or add a role they already have), you MUST inform the user that no changes are necessary and **terminate the workflow immediately**. Do not run a simulation.

### Step 3: Run Policy Simulation

Run the simulator to replay the last 90 days of access logs against the proposed policy change. Execute the exact command for your resource type:

**For Projects:**

```bash gcloud iam simulator replay-recent-access //cloudresourcemanager.googleapis.com/projects/TARGET_PROJECT_ID /tmp/proposed_policy.json --project=TARGET_PROJECT_ID --format=json > /tmp/simulation_results.json ```

**For Folders:**

```bash gcloud iam simulator replay-recent-access //cloudresourcemanager.googleapis.com/folders/TARGET_FOLDER_ID /tmp/proposed_policy.json --format=json > /tmp/simulation_results.json ```

**For Organizations:**

```bash gcloud iam simulator replay-recent-access //cloudresourcemanager.googleapis.com/organizations/TARGET_ORG_ID /tmp/proposed_policy.json --format=json > /tmp/simulation_results.json ```

*(Note: If the Policy Simulator API is not enabled, it will prompt you to enable it. Select Yes. Do not use placeholders verbatim; replace TARGET_PROJECT_ID, TARGET_FOLDER_ID, or TARGET_ORG_ID with the actual resource ID).*

**CRUCIAL SAFETY GATE:** Verify the command exited successfully. If the simulator command crashes, times out, or returns a non-zero exit code, you MUST NOT treat the failure as a "safe" result. Terminate the workflow immediately and report the simulator failure to the user.

### Step 4: Analyze Simulation Results

Analyze the contents of `/tmp/simulation_results.json` using the provided helper script. Do not write custom scripts on the fly. You MUST execute the following command:

```bash python3 scripts/analyze_simulation.py ```

* **SAFE (No Breakage):** If the script outputs `REVOKED_COUNT=0`, the change is safe. * **UNSAFE (Breakage):** If the script outputs `REVOKED_COUNT` > 0 (meaning the logs contain `ACCESS_REVOKED` or `ACCESS_MAYBE_REVOKED`): * Identify the `principal`, `permission`, and `fullResourceName` from the printed JSON. * **Do NOT apply the policy.** * The change will break an active workload. Inform the user of the specific disrupted accesses.

### Step 5: Apply Policy (Only if Safe)

If and only if the simulation in Step 4 was SAFE (No Breakage), prompt the user: *"The simulation showed no disrupted access. Do you want to apply this policy change? (Yes/No)"*.

* **If Yes:** Apply the policy using the correct command for the resource type:

**For Projects:**

```bash gcloud projects set-iam-policy TARGET_PROJECT_ID /tmp/proposed_policy.json ```

**For Folders:**

```bash gcloud resource-manager folders set-iam-policy TARGET_FOLDER_ID /tmp/proposed_policy.json ```

**For Organizations:**

```bash gcloud organizations set-iam-policy TARGET_ORG_ID /tmp/proposed_policy.json ```

* **If No:** Terminate the workflow.

### Step 6: Cleanup (Always Run)

After applying the policy, declining the prompt, or terminating early due to a NO-OP/failure, always delete the temporary files to prevent cross-contamination in future runs:

```bash rm -f /tmp/current_policy.json /tmp/proposed_policy.json /tmp/simulation_results.json ```

Intended uses

  • Use Iam Helper For Policy Simulator when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.