vmware-aiops 2.2.0__tar.gz → 2.3.0__tar.gz

{vmware_aiops-2.2.0 → vmware_aiops-2.3.0}/.claude-plugin/plugin.json

@@ -2,8 +2,8 @@
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "vmware-aiops",
   "displayName": "VMware AIops",
-  "version": "2.2.0",
-  "description": "AI-powered VMware vCenter/ESXi VM lifecycle and deployment with 60 MCP tools.",
+  "version": "2.3.0",
+  "description": "AI-powered VMware vCenter/ESXi VM lifecycle and deployment with 61 MCP tools.",
   "author": {
     "name": "Wei Zhou",
     "email": "zhouwei008@gmail.com",

{vmware_aiops-2.2.0 → vmware_aiops-2.3.0}/.mcp.json

@@ -5,7 +5,7 @@
       "command": "uvx",
       "args": [
         "--from",
-        "vmware-aiops==2.2.0",
+        "vmware-aiops==2.3.0",
         "vmware-aiops-mcp"
       ]
     }

vmware_aiops-2.2.0/README.md → vmware_aiops-2.3.0/PKG-INFO

@@ -1,3 +1,27 @@
+Metadata-Version: 2.5
+Name: vmware-aiops
+Version: 2.3.0
+Summary: VMware vCenter/ESXi AI-powered VM lifecycle and deployment tool
+Project-URL: Homepage, https://github.com/vmware-skills/VMware-AIops
+Project-URL: Repository, https://github.com/vmware-skills/VMware-AIops
+Project-URL: Issues, https://github.com/vmware-skills/VMware-AIops/issues
+Project-URL: Changelog, https://github.com/vmware-skills/VMware-AIops/blob/main/RELEASE_NOTES.md
+Author-email: Wei Zhou <wei-wz.zhou@broadcom.com>
+License-Expression: MIT
+License-File: LICENSE
+Requires-Python: >=3.10
+Requires-Dist: apscheduler<4.0,>=3.10
+Requires-Dist: httpx<1.0,>=0.27
+Requires-Dist: mcp[cli]<2.0,>=1.28
+Requires-Dist: pyaml<27.0,>=24.0
+Requires-Dist: python-dotenv<2.0,>=1.0
+Requires-Dist: pyvmomi<10.0,>=8.0.3.0
+Requires-Dist: rich<16.0,>=13.0
+Requires-Dist: typer<1.0,>=0.12
+Requires-Dist: vmware-monitor<3.0,>=2.0.0
+Requires-Dist: vmware-policy<2.0,>=1.22.0
+Description-Content-Type: text/markdown
+
 <!-- mcp-name: io.github.vmware-skills/vmware-aiops -->
 # VMware AIops
 
@@ -7,7 +31,7 @@
 
 English | [中文](README-CN.md)
 
-AI-powered VMware vCenter/ESXi VM lifecycle and deployment tool — 60 tools.
+AI-powered VMware vCenter/ESXi VM lifecycle and deployment tool — 61 tools.
 
 > **Companion skills** handle everything else:
 >
@@ -26,7 +50,7 @@ AI-powered VMware vCenter/ESXi VM lifecycle and deployment tool — 60 tools.
 
 ## Upgrading to 2.0
 
-2.0 renames 38 of its 60 MCP tools so every name starts with a verb (e.g. `cluster_add_host` → `add_cluster_host`, `cluster_configure` → `configure_cluster`, `cluster_create` → `create_cluster`). The full old → new table is in
+2.0 renames 38 of its MCP tools so every name starts with a verb (e.g. `cluster_add_host` → `add_cluster_host`, `cluster_configure` → `configure_cluster`, `cluster_create` → `create_cluster`). The full old → new table is in
 [RELEASE_NOTES.md](RELEASE_NOTES.md#v200--mcp-tools-renamed-verb-first). Nothing else changes: same tools, parameters,
 safety gates and CLI commands. If an agent prompt, script or `~/.vmware/rules.yaml` names a tool, update it (but not the `action` words in saved plan
 files — `cluster_add_host`, `storage_rescan` and the like are plan actions, not tool names, and keep their spelling) — though deny
@@ -151,6 +175,7 @@ operator an auditor can sign off on, that's what this family is for — see
 | **Cluster** | create, delete, HA/DRS config, add/remove hosts | 6 |
 | **Datastore** | browse files, scan for images | 2 |
 | **Network** | dvSwitch portgroup list/create, host VMkernel list/add/remove, DF-bit MTU-path ping | 6 |
+| **Access** | which account is in use, and whether it holds each tool's privileges (`get_access_info`, CLI `access-info`) | 1 |
 
 ### CLI vs MCP: Which Mode to Use
 
@@ -956,6 +981,7 @@ User → Aider CLI → Ollama (localhost:11434) → Qwen / DeepSeek local model
 # Diagnostics
 vmware-aiops doctor                   # Check environment, config, connectivity
 vmware-aiops doctor --skip-auth       # Skip vSphere auth check (faster)
+vmware-aiops access-info [--tool <mcp-tool>] [--target <name>]  # Account in use + privileges per tool
 
 # MCP Config Generator
 vmware-aiops mcp-config generate --agent goose        # Generate config for Goose
@@ -1122,6 +1148,64 @@ Built on **pyVmomi** (vSphere Web Services API / SOAP).
 
 If you encounter any errors or issues, please send the error message, logs, or screenshots to **zhouwei008@gmail.com**. Contributions are welcome — feel free to join us in maintaining and improving this project!
 
+<!-- usage: remote-and-exposure -->
+## Remote access (HTTPS) and limiting tools
+
+By default `vmware-aiops mcp` speaks stdio to one local client and offers every tool. Two options change that
+(vmware-policy ≥ 1.21.0).
+
+**Serve over HTTPS** so clients on other machines can connect. Every caller needs a bearer token:
+
+```bash
+vmware-audit token create alice          # prints the token once; give it to alice
+vmware-audit token list                  # names only
+vmware-audit token revoke alice          # refused from its next request, no restart
+vmware-aiops mcp --transport https --host 0.0.0.0 --port 8443 \
+    --cert /etc/vmware-mcp/server.pem --key /etc/vmware-mcp/server-key.pem \
+    --public-name mcp.example.com
+```
+
+Connect a client (Claude Code shown; any MCP client that supports streamable HTTP and custom headers works):
+
+```bash
+claude mcp add --transport http vmware-aiops https://mcp.example.com:8443/mcp \
+    --header "Authorization: Bearer $VMWARE_MCP_TOKEN"
+```
+
+```json
+{
+  "mcpServers": {
+    "vmware-aiops": {
+      "type": "http",
+      "url": "https://mcp.example.com:8443/mcp",
+      "headers": { "Authorization": "Bearer ${VMWARE_MCP_TOKEN}" }
+    }
+  }
+}
+```
+
+- The server will not start without a token, refuses Host/Origin values outside `--public-name`, and checks
+  before it binds that unauthenticated requests get 401. Use a certificate your clients trust for those names.
+- Behind a TLS-terminating reverse proxy on the same machine use `--transport http --host 127.0.0.1
+  --public-name mcp.example.com` and pass the `Authorization` header through.
+- The audit log records each caller as `token:<name>`. Calls run side by side, with up to `VMWARE_MCP_POOL_SIZE`
+  (default 2) sessions per target; each session is a login on the target, and a call waits at most 300 s for one.
+- **Everyone who can reach the endpoint acts with this server's account.** Tokens identify callers; they grant
+  nothing on the platform. Run one endpoint per privilege level.
+
+**Offer only read tools, plus the writes you choose:**
+
+```bash
+vmware-aiops mcp --expose read --allow-write acknowledge_vcenter_alarm
+# or: VMWARE_AIOPS_MCP_EXPOSE=read VMWARE_AIOPS_MCP_ALLOW_WRITE=acknowledge_vcenter_alarm vmware-aiops mcp
+```
+
+Tools not offered do not appear in the client's tool list. A bad value or an unknown write tool stops the server
+(exit 2). This limits what clients are offered; it is not authorization, so the account itself should be
+least-privilege.
+
+Details: `skills/vmware-aiops/references/setup-guide.md` ("Serving MCP over HTTPS", "Limiting which tools are offered").
+
 ## License
 
 MIT

{vmware_aiops-2.2.0 → vmware_aiops-2.3.0}/README-CN.md

@@ -7,7 +7,7 @@
 
 [English](README.md) | 中文
 
-AI 驱动的 VMware vCenter/ESXi VM 生命周期管理与部署工具 — 60 个工具。
+AI 驱动的 VMware vCenter/ESXi VM 生命周期管理与部署工具 — 61 个工具。
 
 > **配套技能**负责其他领域：
 >
@@ -26,7 +26,7 @@ AI 驱动的 VMware vCenter/ESXi VM 生命周期管理与部署工具 — 60 个
 
 ## 升级到 2.0
 
-2.0 把 60 个 MCP 工具中的 38 个改成动词在前（例如 `cluster_add_host` → `add_cluster_host`, `cluster_configure` → `configure_cluster`, `cluster_create` → `create_cluster`），完整的新旧名对照表见
+2.0 把 MCP 工具名改成动词在前（共改名 38 处）（例如 `cluster_add_host` → `add_cluster_host`, `cluster_configure` → `configure_cluster`, `cluster_create` → `create_cluster`），完整的新旧名对照表见
 [RELEASE_NOTES.md](RELEASE_NOTES.md#v200--mcp-tools-renamed-verb-first)。其他都不变：工具、参数、安全确认门和 CLI 命令都一样。
 如果 agent 提示词、脚本或 `~/.vmware/rules.yaml` 里写了工具名，请改成新名（但已保存计划文件里的 `action` 动作词不要改——`cluster_add_host`、`storage_rescan` 这类是计划动作，不是工具名，保持原样）——不过用旧名写的 deny 规则在
 vmware-policy ≥ 1.18 下仍然生效（`vmware-audit policy` 会列出因改名而多匹配的规则），vmware-pilot ≥ 1.13 也会自动转换已保存工作流里的旧名。
@@ -118,12 +118,13 @@ pip install --no-index --find-links dist vmware-aiops
 | **集群** | 创建、删除、HA/DRS 配置、添加/移除主机 | 6 |
 | **数据存储** | 浏览文件、扫描镜像 | 2 |
 | **网络** | dvSwitch 端口组 列出/创建、主机 VMkernel 列出/添加/移除、DF 位 MTU 路径 ping | 6 |
+| **权限** | 当前使用哪个账号，以及它是否具备每个工具所需的权限（`get_access_info`，CLI `access-info`） | 1 |
 
 ### CLI vs MCP：如何选择
 
 | 场景 | 推荐模式 | 原因 |
 |------|:-------:|------|
-| **本地/小模型**（Ollama、Qwen <32B） | **CLI** | 上下文占用 ~2K tokens vs MCP ~10K；小模型难以处理 60 个工具的 schema |
+| **本地/小模型**（Ollama、Qwen <32B） | **CLI** | 上下文占用 ~2K tokens vs MCP ~10K；小模型难以处理 61 个工具的 schema |
 | **Token 敏感场景** | **CLI** | SKILL.md + Bash = 最小开销 |
 | **云端大模型**（Claude、GPT-4o） | 均可 | MCP 提供结构化 JSON 输入输出 |
 | **自动化管道 / Agent 链式调用** | **MCP** | 类型安全参数，结构化输出，无需 Shell 解析 |
@@ -665,6 +666,7 @@ aider --conventions skills/vmware-aiops/SKILL.md --model ollama/qwen2.5-coder:32
 # 环境诊断
 vmware-aiops doctor                   # 检查环境、配置、连通性
 vmware-aiops doctor --skip-auth       # 跳过 vSphere 认证检查（更快）
+vmware-aiops access-info [--tool <mcp-tool>] [--target <name>]  # 当前账号 + 每个工具的权限
 
 # MCP 配置生成
 vmware-aiops mcp-config generate --agent goose        # 生成 Goose 配置
@@ -787,6 +789,63 @@ VMware-AIops/
 
 If you encounter any errors or issues, please send the error message, logs, or screenshots to **zhouwei008@gmail.com**. Contributions are welcome — feel free to join us in maintaining and improving this project!
 
+<!-- usage: remote-and-exposure -->
+## 远程访问（HTTPS）与限制工具
+
+默认情况下 `vmware-aiops mcp` 通过 stdio 服务一个本地客户端，并提供全部工具。以下两个选项可以改变这一点
+（需 vmware-policy ≥ 1.21.0）。
+
+**通过 HTTPS 提供服务**，让其他机器上的客户端连接。每个调用者都需要一个 bearer token：
+
+```bash
+vmware-audit token create alice          # 只显示一次，交给 alice
+vmware-audit token list                  # 只列名字
+vmware-audit token revoke alice          # 下一个请求起即拒绝，无需重启
+vmware-aiops mcp --transport https --host 0.0.0.0 --port 8443 \
+    --cert /etc/vmware-mcp/server.pem --key /etc/vmware-mcp/server-key.pem \
+    --public-name mcp.example.com
+```
+
+连接客户端（以 Claude Code 为例；任何支持 streamable HTTP 和自定义请求头的 MCP 客户端都可以）：
+
+```bash
+claude mcp add --transport http vmware-aiops https://mcp.example.com:8443/mcp \
+    --header "Authorization: Bearer $VMWARE_MCP_TOKEN"
+```
+
+```json
+{
+  "mcpServers": {
+    "vmware-aiops": {
+      "type": "http",
+      "url": "https://mcp.example.com:8443/mcp",
+      "headers": { "Authorization": "Bearer ${VMWARE_MCP_TOKEN}" }
+    }
+  }
+}
+```
+
+- 没有 token 时服务不会启动；`--public-name` 之外的 Host/Origin 一律拒绝；绑定端口前会自检，确认未认证请求得到 401。
+  证书要用客户端信任、且覆盖这些名字的证书。
+- 在同一台机器上由反向代理终结 TLS 时，用 `--transport http --host 127.0.0.1 --public-name mcp.example.com`，
+  并让代理透传 `Authorization` 头。
+- 审计日志把每个调用者记为 `token:<名字>`。调用并行执行，每个 target 最多 `VMWARE_MCP_POOL_SIZE`（默认 2）
+  个会话；每个会话都是在该 target 上的一次登录，一个调用最多等待 300 秒拿到会话。
+- **能连到这个端点的人，都以该 server 配置的账号操作。** token 只用来识别调用者，不在平台上授予任何权限。
+  每个权限级别单独起一个端点。
+
+**只提供读工具，加上你选定的写工具：**
+
+```bash
+vmware-aiops mcp --expose read --allow-write acknowledge_vcenter_alarm
+# 或：VMWARE_AIOPS_MCP_EXPOSE=read VMWARE_AIOPS_MCP_ALLOW_WRITE=acknowledge_vcenter_alarm vmware-aiops mcp
+```
+
+未提供的工具不会出现在客户端的工具列表里。取值错误或写工具名不存在时服务直接退出（exit 2）。
+这只限制提供给客户端的工具，不是授权；账号本身仍应遵循最小权限。
+
+详见 `skills/vmware-aiops/references/setup-guide.md`（"Serving MCP over HTTPS"、"Limiting which tools are offered"）。
+
 ## 许可证
 
 MIT

vmware_aiops-2.2.0/PKG-INFO → vmware_aiops-2.3.0/README.md

@@ -1,27 +1,3 @@
-Metadata-Version: 2.5
-Name: vmware-aiops
-Version: 2.2.0
-Summary: VMware vCenter/ESXi AI-powered VM lifecycle and deployment tool
-Project-URL: Homepage, https://github.com/vmware-skills/VMware-AIops
-Project-URL: Repository, https://github.com/vmware-skills/VMware-AIops
-Project-URL: Issues, https://github.com/vmware-skills/VMware-AIops/issues
-Project-URL: Changelog, https://github.com/vmware-skills/VMware-AIops/blob/main/RELEASE_NOTES.md
-Author-email: Wei Zhou <wei-wz.zhou@broadcom.com>
-License-Expression: MIT
-License-File: LICENSE
-Requires-Python: >=3.10
-Requires-Dist: apscheduler<4.0,>=3.10
-Requires-Dist: httpx<1.0,>=0.27
-Requires-Dist: mcp[cli]<2.0,>=1.28
-Requires-Dist: pyaml<27.0,>=24.0
-Requires-Dist: python-dotenv<2.0,>=1.0
-Requires-Dist: pyvmomi<10.0,>=8.0.3.0
-Requires-Dist: rich<16.0,>=13.0
-Requires-Dist: typer<1.0,>=0.12
-Requires-Dist: vmware-monitor<3.0,>=2.0.0
-Requires-Dist: vmware-policy<2.0,>=1.21.0
-Description-Content-Type: text/markdown
-
 <!-- mcp-name: io.github.vmware-skills/vmware-aiops -->
 # VMware AIops
 
@@ -31,7 +7,7 @@ Description-Content-Type: text/markdown
 
 English | [中文](README-CN.md)
 
-AI-powered VMware vCenter/ESXi VM lifecycle and deployment tool — 60 tools.
+AI-powered VMware vCenter/ESXi VM lifecycle and deployment tool — 61 tools.
 
 > **Companion skills** handle everything else:
 >
@@ -50,7 +26,7 @@ AI-powered VMware vCenter/ESXi VM lifecycle and deployment tool — 60 tools.
 
 ## Upgrading to 2.0
 
-2.0 renames 38 of its 60 MCP tools so every name starts with a verb (e.g. `cluster_add_host` → `add_cluster_host`, `cluster_configure` → `configure_cluster`, `cluster_create` → `create_cluster`). The full old → new table is in
+2.0 renames 38 of its MCP tools so every name starts with a verb (e.g. `cluster_add_host` → `add_cluster_host`, `cluster_configure` → `configure_cluster`, `cluster_create` → `create_cluster`). The full old → new table is in
 [RELEASE_NOTES.md](RELEASE_NOTES.md#v200--mcp-tools-renamed-verb-first). Nothing else changes: same tools, parameters,
 safety gates and CLI commands. If an agent prompt, script or `~/.vmware/rules.yaml` names a tool, update it (but not the `action` words in saved plan
 files — `cluster_add_host`, `storage_rescan` and the like are plan actions, not tool names, and keep their spelling) — though deny
@@ -175,6 +151,7 @@ operator an auditor can sign off on, that's what this family is for — see
 | **Cluster** | create, delete, HA/DRS config, add/remove hosts | 6 |
 | **Datastore** | browse files, scan for images | 2 |
 | **Network** | dvSwitch portgroup list/create, host VMkernel list/add/remove, DF-bit MTU-path ping | 6 |
+| **Access** | which account is in use, and whether it holds each tool's privileges (`get_access_info`, CLI `access-info`) | 1 |
 
 ### CLI vs MCP: Which Mode to Use
 
@@ -980,6 +957,7 @@ User → Aider CLI → Ollama (localhost:11434) → Qwen / DeepSeek local model
 # Diagnostics
 vmware-aiops doctor                   # Check environment, config, connectivity
 vmware-aiops doctor --skip-auth       # Skip vSphere auth check (faster)
+vmware-aiops access-info [--tool <mcp-tool>] [--target <name>]  # Account in use + privileges per tool
 
 # MCP Config Generator
 vmware-aiops mcp-config generate --agent goose        # Generate config for Goose
@@ -1146,6 +1124,64 @@ Built on **pyVmomi** (vSphere Web Services API / SOAP).
 
 If you encounter any errors or issues, please send the error message, logs, or screenshots to **zhouwei008@gmail.com**. Contributions are welcome — feel free to join us in maintaining and improving this project!
 
+<!-- usage: remote-and-exposure -->
+## Remote access (HTTPS) and limiting tools
+
+By default `vmware-aiops mcp` speaks stdio to one local client and offers every tool. Two options change that
+(vmware-policy ≥ 1.21.0).
+
+**Serve over HTTPS** so clients on other machines can connect. Every caller needs a bearer token:
+
+```bash
+vmware-audit token create alice          # prints the token once; give it to alice
+vmware-audit token list                  # names only
+vmware-audit token revoke alice          # refused from its next request, no restart
+vmware-aiops mcp --transport https --host 0.0.0.0 --port 8443 \
+    --cert /etc/vmware-mcp/server.pem --key /etc/vmware-mcp/server-key.pem \
+    --public-name mcp.example.com
+```
+
+Connect a client (Claude Code shown; any MCP client that supports streamable HTTP and custom headers works):
+
+```bash
+claude mcp add --transport http vmware-aiops https://mcp.example.com:8443/mcp \
+    --header "Authorization: Bearer $VMWARE_MCP_TOKEN"
+```
+
+```json
+{
+  "mcpServers": {
+    "vmware-aiops": {
+      "type": "http",
+      "url": "https://mcp.example.com:8443/mcp",
+      "headers": { "Authorization": "Bearer ${VMWARE_MCP_TOKEN}" }
+    }
+  }
+}
+```
+
+- The server will not start without a token, refuses Host/Origin values outside `--public-name`, and checks
+  before it binds that unauthenticated requests get 401. Use a certificate your clients trust for those names.
+- Behind a TLS-terminating reverse proxy on the same machine use `--transport http --host 127.0.0.1
+  --public-name mcp.example.com` and pass the `Authorization` header through.
+- The audit log records each caller as `token:<name>`. Calls run side by side, with up to `VMWARE_MCP_POOL_SIZE`
+  (default 2) sessions per target; each session is a login on the target, and a call waits at most 300 s for one.
+- **Everyone who can reach the endpoint acts with this server's account.** Tokens identify callers; they grant
+  nothing on the platform. Run one endpoint per privilege level.
+
+**Offer only read tools, plus the writes you choose:**
+
+```bash
+vmware-aiops mcp --expose read --allow-write acknowledge_vcenter_alarm
+# or: VMWARE_AIOPS_MCP_EXPOSE=read VMWARE_AIOPS_MCP_ALLOW_WRITE=acknowledge_vcenter_alarm vmware-aiops mcp
+```
+
+Tools not offered do not appear in the client's tool list. A bad value or an unknown write tool stops the server
+(exit 2). This limits what clients are offered; it is not authorization, so the account itself should be
+least-privilege.
+
+Details: `skills/vmware-aiops/references/setup-guide.md` ("Serving MCP over HTTPS", "Limiting which tools are offered").
+
 ## License
 
 MIT

{vmware_aiops-2.2.0 → vmware_aiops-2.3.0}/RELEASE_NOTES.md

@@ -1,3 +1,23 @@
+## v2.3.0 — calls on one target run side by side; `get_access_info`
+
+Needs vmware-policy 1.22.0.
+
+* **Calls no longer queue behind each other on a shared server.** Served over `--transport https`/`http`,
+  calls run side by side with up to `VMWARE_MCP_POOL_SIZE` (default 2) sessions per target; each call holds its
+  own session for its whole run, so two calls never share one. Each session is a login on the target. A call
+  that finds every session busy waits at most 300 s, then fails with a message saying so. stdio and the CLI
+  keep one session per target, as before.
+* **Side-by-side calls no longer race on local state.** Two TTL changes at once could drop each other's entry
+  (and a reader catching the file mid-write saw no entries at all); the TTL store and the image registry are now
+  written atomically and TTL updates are serialized. One plan can no longer be applied or rolled back by two
+  calls at once: the second is refused with a message, and nothing runs twice.
+* **The daemon's scan and TTL check each use their own session.** They run on APScheduler's thread pool and
+  could overlap on one pyVmomi session.
+* **New tool `get_access_info`** (CLI `vmware-aiops access-info [--tool X] [--target T]`): which account the
+  server uses on a target, and whether it holds the privileges each tool needs, e.g. `--tool clone_vm`. It asks
+  vCenter about its own session (System.View is enough). Checked on the root folder: `not_granted_at_root` can
+  still be granted on a cluster, folder or VM, and `undetermined` is never read as granted. 61 tools (was 60).
+
 ## v2.2.0 — serve MCP over HTTPS
 
 `vmware-aiops mcp` can now serve the network as well as stdio (HLD §16, via vmware-policy 1.21.0):
@@ -8,6 +28,15 @@ vmware-aiops mcp --transport https --host 0.0.0.0 --port 8443 \
     --cert server.pem --key server-key.pem --public-name mcp.example.com
 ```
 
+Connect a client and manage callers (Claude Code shown; any MCP client with streamable HTTP and custom headers works):
+
+```bash
+claude mcp add --transport http vmware-aiops https://mcp.example.com:8443/mcp \
+    --header "Authorization: Bearer $VMWARE_MCP_TOKEN"
+vmware-audit token list                  # names only
+vmware-audit token revoke alice          # refused from its next request, no restart
+```
+
 * Every request needs `Authorization: Bearer <token>`; the server will not start without a token, refuses Host or
   Origin values outside `--public-name`, and checks itself (unauthenticated requests must get 401) before it
   binds. `--transport http` binds loopback only, for a TLS-terminating reverse proxy.

{vmware_aiops-2.2.0 → vmware_aiops-2.3.0}/openclaw.plugin.json

@@ -1,7 +1,7 @@
 {
   "id": "vmware-aiops",
   "name": "VMware AIops",
-  "description": "AI-powered VMware vCenter/ESXi VM lifecycle and deployment with 60 MCP tools.",
+  "description": "AI-powered VMware vCenter/ESXi VM lifecycle and deployment with 61 MCP tools.",
   "skills": [
     "./skills"
   ],
@@ -11,7 +11,7 @@
       "command": "uvx",
       "args": [
         "--from",
-        "vmware-aiops==2.2.0",
+        "vmware-aiops==2.3.0",
         "vmware-aiops-mcp"
       ]
     }

{vmware_aiops-2.2.0 → vmware_aiops-2.3.0}/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@zw008/vmware-aiops",
-  "version": "2.2.0",
-  "description": "AI-powered VMware vCenter/ESXi VM lifecycle and deployment with 60 MCP tools.",
+  "version": "2.3.0",
+  "description": "AI-powered VMware vCenter/ESXi VM lifecycle and deployment with 61 MCP tools.",
   "private": true,
   "license": "MIT",
   "homepage": "https://github.com/vmware-skills/VMware-AIops",

{vmware_aiops-2.2.0 → vmware_aiops-2.3.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "vmware-aiops"
-version = "2.2.0"
+version = "2.3.0"
 description = "VMware vCenter/ESXi AI-powered VM lifecycle and deployment tool"
 readme = "README.md"
 license = "MIT"
@@ -19,7 +19,7 @@ dependencies = [
     "httpx>=0.27,<1.0",
     "python-dotenv>=1.0,<2.0",
     "mcp[cli]>=1.28,<2.0",
-    "vmware-policy>=1.21.0,<2.0",
+    "vmware-policy>=1.22.0,<2.0",
     # Read-only cluster-health triage (summary + HTML snapshot) is owned by
     # vmware-monitor; AIops delegates to it so a conversation with the AIops
     # entry point can produce the same report without duplicating the code.

{vmware_aiops-2.2.0 → vmware_aiops-2.3.0}/server.json

@@ -2,17 +2,17 @@
   "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.vmware-skills/vmware-aiops",
   "title": "VMware AIops",
-  "description": "AI-powered VMware vCenter/ESXi VM lifecycle and deployment with 60 MCP tools.",
+  "description": "AI-powered VMware vCenter/ESXi VM lifecycle and deployment with 61 MCP tools.",
   "repository": {
     "url": "https://github.com/vmware-skills/VMware-AIops",
     "source": "github"
   },
-  "version": "2.2.0",
+  "version": "2.3.0",
   "packages": [
     {
       "registryType": "pypi",
       "identifier": "vmware-aiops",
-      "version": "2.2.0",
+      "version": "2.3.0",
       "runtimeHint": "uvx",
       "packageArguments": [
         {

{vmware_aiops-2.2.0 → vmware_aiops-2.3.0}/skills/vmware-aiops/SKILL.md

@@ -27,7 +27,7 @@ compatibility: >
 
 > **Disclaimer**: This is a community-maintained open-source project and is **not affiliated with, endorsed by, or sponsored by VMware, Inc. or Broadcom Inc.** "VMware" and "vSphere" are trademarks of Broadcom. Source code is publicly auditable at [github.com/vmware-skills/VMware-AIops](https://github.com/vmware-skills/VMware-AIops) under the MIT license.
 
-VMware family entry point — AI-powered VM lifecycle, deployment, and alarm management — 60 MCP tools.
+VMware family entry point — AI-powered VM lifecycle, deployment, and alarm management — 61 MCP tools.
 
 > **Start here**: install vmware-aiops first, then add modules as needed.
 > Run `vmware-aiops hub status` to see which family members are installed.
@@ -47,6 +47,7 @@ VMware family entry point — AI-powered VM lifecycle, deployment, and alarm man
 | **Network** | dvSwitch portgroup list/create, host VMkernel list/add/remove/tag-service, DF-bit MTU-path ping | 7 |
 | **Alarm Management** | list alarms, acknowledge, reset | 3 |
 | **Triage & Investigation** (read-only, delegates to vmware-monitor) | one-glance cluster health summary, object-centered VM/host/datastore drill-down bundles, cross-vCenter "what needs attention now?" | 5 |
+| **Access** | which account is in use, and whether it holds each tool's privileges | 1 |
 
 ## Audit & Safety
 
@@ -62,7 +63,7 @@ Read before connecting an agent. Per-tool inventory: `references/capabilities.md
 ## Quick Install
 
 ```bash
-uv tool install vmware-aiops==2.2.0
+uv tool install vmware-aiops==2.3.0
 vmware-aiops doctor
 vmware-aiops hub status   # see which family members are installed
 ```
@@ -117,7 +118,7 @@ vmware-aiops is the entry point. Add modules for additional capabilities:
 
 ## Common Workflows
 
-> **Diagnostic investigations**: Before remediating any "why is X slow / failing / down" issue, follow [`references/investigation-protocol.md`](references/investigation-protocol.md). It enforces the four root-cause completeness criteria (falsifiability / sufficiency / necessity / mechanism) and the up-to-three-rounds deepening loop. Only invoke L3+ write tools after the four criteria are satisfied AND the user has approved a remediation plan.
+> **Diagnostic investigations**: Before remediating any "why is X slow / failing / down" issue, follow [`references/investigation-protocol.md`](references/investigation-protocol.md). It enforces four root-cause completeness criteria and a deepening loop. Only invoke L3+ write tools after the four criteria are satisfied AND the user has approved a remediation plan.
 
 ### Cluster Health Triage ("what's wrong right now?")
 
@@ -125,7 +126,7 @@ Start here when the ask is "is anything on fire?" before diving into a specific
 
 1. One glance --> `get_cluster_health_summary` (MCP) or `vmware-aiops summary` (CLI). Read `top_issues` first — ranked anomalies (disconnected hosts, red/yellow alarms, capacity pressure), each with a drill-down hint; the per-cluster table is context
 2. Act on what it surfaces --> a `host_down` row → investigate the host; an alarm → `acknowledge_vcenter_alarm` / `reset_vcenter_alarm`; a hot VM implicated → `migrate_vm` or `reconfigure_vm` (after the investigation protocol)
-3. Save/share a snapshot --> `vmware-aiops summary --html` writes an offline, timestamped HTML file (identical to `vmware-monitor summary --html` — same shared renderer)
+3. Save/share a snapshot --> `vmware-aiops summary --html` writes an offline, timestamped HTML file (same renderer as vmware-monitor)
 4. **If vmware-monitor is not installed** --> this command/tool is unavailable (AIops delegates to it); install `vmware-monitor`, or use the deeper per-object read tools in that skill
 
 ### Object-Centered Investigation → Act (drill-down before you change anything)
@@ -143,7 +144,7 @@ Start here when the ask is "is anything on fire?" before diving into a specific
 ### Deploy a Lab Environment
 
 **Pre-flight (judgment, not blind sequence)**:
-- Free space: target datastore must have ≥ OVA size × 2 (delta files + thin-provision overhead). If multiple datastores qualify, prefer one with lowest current IOPS pressure (cross-check `vmware-aria` if available).
+- Free space: target datastore must have ≥ OVA size × 2 (delta files + thin-provision overhead).
 - Name hygiene: prefix with date or owner (`lab-2026-04-30-alice`) so the TTL cleanup audit trail is meaningful.
 - TTL: always set. 480 min for a single test session, 7200 min for a week-long sandbox. **Never deploy a "lab" VM without a TTL** — that is how datastores fill up at 3 AM.
 - Snapshot timing: take the baseline **after** provisioning succeeds, not before — a pre-provision snapshot is just an empty checkpoint.
@@ -161,8 +162,9 @@ Start here when the ask is "is anything on fire?" before diving into a specific
 - Source VM state: powered-off is safest. If powered-on, VMware Tools must be running and quiesce-capable, else clones may have inconsistent disk state.
 - Capacity math: `free_space ≥ source.size × count × 1.2` (full clone) or `≥ count × 2 GB` (linked clone, delta-only).
 - Decision rule: **count > 10 → use linked clones** (`deploy linked-clone`); seconds vs minutes per clone, ~100× less storage. Tradeoff: linked clones depend on source snapshot — deleting the snapshot breaks all children.
-- Network exhaustion: each clone gets a unique MAC from the vSphere pool; if you batch > 200, verify pool capacity in advance.
+- Network: batches > 200 can exhaust the vSphere MAC pool.
 - TTL: every clone must have one. Use the plan's metadata to track ownership.
+- Privileges: `get_access_info(tool="clone_vm")` (CLI `vmware-aiops access-info --tool clone_vm`) — root folder only; `undetermined` is not granted.
 
 **Steps**:
 1. `create_vm_plan` with clone + reconfigure + set-ttl steps grouped per VM (atomic per clone)
@@ -193,7 +195,7 @@ Start here when the ask is "is anything on fire?" before diving into a specific
 | Cloud models (Claude, GPT-4o) | Either | MCP gives structured JSON I/O |
 | Automated pipelines | **MCP** | Type-safe parameters, structured output |
 
-## MCP Tools (60 — 17 read, 43 write)
+## MCP Tools (61 — 18 read, 43 write)
 
 | Category | Tools | R/W |
 |----------|-------|:---:|
@@ -212,10 +214,11 @@ Start here when the ask is "is anything on fire?" before diving into a specific
 | | `acknowledge_vcenter_alarm`, `reset_vcenter_alarm` | Write |
 | Cluster Triage (1) | `get_cluster_health_summary` (delegates to vmware-monitor) | Read |
 | Object Investigation (4) | `investigate_vm`, `investigate_host`, `investigate_datastore`, `get_cross_vcenter_attention` (all delegate to vmware-monitor) | Read |
+| Access (1) | `get_access_info` | Read |
 
 **List envelope**: the read list tools — `browse_datastore`, `list_vcenter_alarms`, `list_vm_plans`, `list_vm_snapshots`, `list_vm_ttls` — return `{items, returned, limit, total, truncated, hint}` rather than a bare array. Read the rows from `items` and check `truncated` before concluding a listing is complete; empty `items` with `truncated: false` means checked-and-none, not a failure. The write `batch_*` tools keep their bare list (complete by construction). Rationale, `total` semantics, error shape: `references/capabilities.md`.
 
-**Read/write split**: 17 tools are read-only (per `[READ]` docstring marker), 43 modify state — gating in [Audit & Safety](#audit--safety). `set_vm_ttl` schedules an unattended auto-delete.
+**Read/write split**: 18 tools are read-only (per `[READ]` docstring marker), 43 modify state — gating in [Audit & Safety](#audit--safety). `set_vm_ttl` schedules an unattended auto-delete.
 
 **Network write gating**: all four network writes are preview/confirm-gated — `confirm=False` (default) returns the exact spec without writing. `remove_host_vmk` is **fail-closed**: it refuses when the vmk is selected for a host service (management/vMotion/vSAN), lives on a non-default netstack (NSX TEPs, dedicated vMotion stacks), carries a default gateway route, or when any of that cannot be verified — pass `force_unprotected=True` to override the non-absolute protections. The host's only management-enabled vmk is never removable (no override). `set_vmk_service` is **fail-closed** too: it refuses both directions when the host's service map is unreadable, and refuses (no override) to untag `management` from the host's only management-enabled vmk — the call rides the interface it would untag.
 
@@ -298,7 +301,7 @@ Run `vmware-aiops plan list` to see failed plan status. Ask user if they want to
 ## Setup
 
 ```bash
-uv tool install vmware-aiops==2.2.0
+uv tool install vmware-aiops==2.3.0
 mkdir -p ~/.vmware-aiops
 vmware-aiops init  # generates config.yaml and .env templates
 chmod 600 ~/.vmware-aiops/.env

{vmware_aiops-2.2.0 → vmware_aiops-2.3.0}/skills/vmware-aiops/references/agent-guardrails.md

@@ -14,7 +14,7 @@ vmware-monitor and vmware-aria against a production vSphere estate with Llama
 cross-skill rules are identical across this family; the parts below marked
 vmware-aiops are specific to this skill.
 
-vmware-aiops carries the family's largest write surface — 43 of its 60 MCP
+vmware-aiops carries the family's largest write surface — 43 of its 61 MCP
 tools change state, including `delete_vm`, cluster deletion, host VMkernel
 removal and guest command execution. Of every skill here, this is the one where a model's discipline
 should not be the only thing standing between a prompt and a destroyed VM — and

{vmware_aiops-2.2.0 → vmware_aiops-2.3.0}/skills/vmware-aiops/references/capabilities.md

@@ -291,6 +291,29 @@ MCP-only (no CLI subcommand). Seven tools for distributed-switch portgroup and h
 
 > **Blast radius**: vSphere has no per-alarm clear API. `alarm reset` / `reset_vcenter_alarm` uses `AlarmManager.ClearTriggeredAlarms`, which clears **all** triggered alarms matching the named alarm's entity type (host/VM/all) and current status (red/yellow) — not just the named one. The named alarm is looked up first (typos fail fast). Over MCP a bare call previews every alarm it would clear (`blast_radius.will_clear`) and changes nothing; `confirm=True` clears, and the result's `scope` field reports exactly what was cleared. Cleared alarms re-trigger automatically if their underlying condition persists.
 
+## Access self-check — `get_access_info`
+
+`get_access_info(tool=None, target=None)` (CLI `access-info`) asks the target about this
+server's own session (`HasPrivilegeOnEntities`, which needs only System.View) and answers
+which account it acts as and whether that account holds the privileges a tool needs: with
+`tool`, `{name, requires, verdict, meaning, missing_at_root}`; without it, every tool sorted
+into `tools_granted_at_root` / `tools_not_granted_at_root` / `tools_undetermined` /
+`tools_no_privilege_needed`, plus the account's direct permissions. Use it before a write
+the account may not be allowed, or after a NoPermission. The table it reads is
+`vmware_aiops/access_requirements.py`.
+
+- Checked on the **root folder** only. `not_granted_at_root` may still be granted on a
+  cluster, folder or VM; `undetermined` (the platform did not answer) is never granted.
+- Where vSphere checks a privilege inside the method (reconfigure, clone from a template,
+  vMotion, cluster delete, datastore browse), the table lists vSphere's documented id.
+  `ping_from_vmk` (esxcli through the host) is always `undetermined`: what the host checks
+  for it is not documented.
+- `set_vm_ttl` includes what `delete_vm` needs: the daemon deletes later as this account.
+- `apply_vm_plan` / `rollback_vm_plan` list every privilege any plan step could need; a
+  given plan needs only its own steps'.
+
+**Typical response tokens**: ~310 for one tool, ~900 for all 61.
+
 ## Scheduled Scanning & Notifications
 
 | Feature | Details |

{vmware_aiops-2.2.0 → vmware_aiops-2.3.0}/skills/vmware-aiops/references/cli-reference.md

@@ -9,6 +9,7 @@ default, the other 20 write tools act immediately, and the enforcement boundary
 ```bash
 # Diagnostics
 vmware-aiops doctor [--skip-auth]   # --skip-auth only skips doctor's own vSphere login check; no other command has it
+vmware-aiops access-info [--tool <mcp-tool>] [--target <name>]   # account in use + its privileges per MCP tool (JSON; root folder only)
 
 # MCP Config Generator
 vmware-aiops mcp-config generate --agent <goose|cursor|claude-code|continue|vscode-copilot|localcowork|mcp-agent>