{ "SchemaVersion": "1", "Kind": "DirectoryIssues", "Slug": "automox-mcp-server", "Name": "Automox MCP Server", "CanonicalUrl": "https://askpod.ai/mcp/automox-mcp-server/issues", "ServerUrl": "https://askpod.ai/mcp/automox-mcp-server", "IssueTotal": 42, "Held": 23, "Issues": [ { "Title": "execute_device_command patch_specific sends `args` as an array; live API requires a string (HTTP 400)", "Excerpt": "## Summary\n\n`execute_device_command` with `command_type=\"patch_specific\"` (`InstallUpdate`) can serialize the `args` field as a **JSON array**, but the live Automox device-queue endpoint requires `args` to be a **string**. An array is rejected upstream with:\n\n```json\n{\"errors\":[\"The args must be a string.\"]}\n```\n(HTTP 400)\n\n## Endpoint\n\n`POST /servers/{id}/queues?o={org}` with `command_type_name: \"InstallUpdate\"`.\n\n## Reproduction\n\nQueue `InstallUpdate` with `args` as an array of patch names:\n\n`", "SourceUrl": "https://github.com/AutomoxCommunity/automox-mcp/issues/234", "PublishedAt": "2026-06-30T14:27:15.000Z", "State": "open", "Comments": 0, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Bug: list_zone_users returns empty {} for all user objects (field name mismatch)", "Excerpt": "## Description\n\nThe `list_zone_users` tool returns the correct user *count* for a zone, but every user object in the results is empty `{}`. No user data (name, email, role, etc.) is returned.\n\n## Root Cause\n\nIn `automox_mcp/workflows/account.py`, the `_ZONE_USER_FIELDS` constant uses camelCase-style field names (`firstname`, `lastname`), but the Automox `/accounts/{id}/zones/{zone_id}/users` API endpoint returns snake_case fields (`first_name`, `last_name`). The `_project()` function finds no ma", "SourceUrl": "https://github.com/AutomoxCommunity/automox-mcp/issues/226", "PublishedAt": "2026-06-18T16:18:31.000Z", "State": "open", "Comments": 0, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "discover_capabilities: make discovery runtime-aware and self-checking (diverges from callable registry)", "Excerpt": "## Summary\n\nA field reconciliation of `discover_capabilities` output (v2.2.1, Claude Desktop session: no-arg call + all 17 domains, script-validated against the session's exposed tool surface) confirmed the catalog is **arithmetically correct** — all 17 `tool_count` values match their list lengths, and the discovery set reconciles exactly to the registered set (133 = 132 catalog-unique + `discover_capabilities`; the session's 129-tool surface = 133 − 4 env-gated). But the exercise surfaced real ", "SourceUrl": "https://github.com/AutomoxCommunity/automox-mcp/issues/217", "PublishedAt": "2026-06-10T18:00:26.000Z", "State": "closed", "Comments": 0, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Sanitizer corrupts worklet code fields; patch policies created without filter_type (API 400)", "Excerpt": "## Summary\nTwo bugs in the MCP server break worklet/patch-policy workflows. They were found together while creating worklets and a \"patch all\" policy.\n\n---\n\n### Bug 1 — Response sanitizer silently corrupts code fields (display)\n`sanitize_for_llm` / `sanitize_dict` (`src/automox_mcp/utils/sanitize.py`), applied to every tool response via `as_tool_response` (`src/automox_mcp/utils/tooling.py`), runs a markdown-link strip `[text](url)` -> `text`. This matches PowerShell type-casts:\n\n- `\\$x = [bool]", "SourceUrl": "https://github.com/AutomoxCommunity/automox-mcp/issues/206", "PublishedAt": "2026-06-08T20:03:17.000Z", "State": "closed", "Comments": 0, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Account-user UUID gap: UUID-keyed account tools have no sanctioned UUID-producing listing", "Excerpt": "## Problem / why\n\n`get_account_user`, `remove_user_from_account`, and `list_zones_for_user` are keyed by an account-user UUID (`user_id: str`), but no sanctioned listing surfaces that UUID — `list_users` / `get_user` project a numeric `id` and deliberately omit `uuid` (`_USER_LIST_FIELDS`, `workflows/account.py`). So these three tools are effectively unreachable without an out-of-band UUID, which also blocks any \"remove user from account\" certification action (#182).\n\n## Secondary finding — fixe", "SourceUrl": "https://github.com/AutomoxCommunity/automox-mcp/issues/193", "PublishedAt": "2026-06-08T04:47:57.000Z", "State": "open", "Comments": 0, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "MCP App (#182 follow-up): wire API-key revocation as the access-certification act lever", "Excerpt": "## Problem / why\n\n#182 (access certification) shipped read-only — review of users/roles. The \"act on a failed certification\" half was deferred. Role *change* has no API tool (`update_user` is profile-only — firstname/lastname/email/tfa_type; role is set only at invite via `invite_user_to_account(account_rbac_role=...)`), and account membership-revoke is UUID-stranded (see the UUID-gap issue) — but **API-key revocation is fully available today and numeric-keyed**, so it's the one actionable revok", "SourceUrl": "https://github.com/AutomoxCommunity/automox-mcp/issues/192", "PublishedAt": "2026-06-08T04:47:56.000Z", "State": "open", "Comments": 0, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Epic: MCP Apps — approval/review surfaces", "Excerpt": "## Why\n\nShip interactive `ui://` **App** surfaces that fill gaps a static tool response (and the console GUI) don't cover — inline review/approval before consequential writes — with graceful degradation to structured output on non-Apps hosts. Sequenced **read-only → write** so the safe pilot establishes the pattern first.\n\n## Constraint\n\n`prefab_ui` is not installed → use the **dependency-free** `ui://` HTML resource + `AppConfig` path (no Prefab Component dependency).\n\n## Sub-issues (sequenced)", "SourceUrl": "https://github.com/AutomoxCommunity/automox-mcp/issues/184", "PublishedAt": "2026-06-08T00:07:58.000Z", "State": "closed", "Comments": 1, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Epic: Structured output (outputSchema) across tools", "Excerpt": "## Why\n\nAdvertise a per-tool `outputSchema` so schema-aware MCP clients can validate our `{\"data\",\"metadata\"}` envelopes and render them richly, and so the App surfaces (see the MCP Apps epic) can consume typed structured output. Today the envelope is attached as `structuredContent`, but no schema is advertised, so clients can't rely on the shape.\n\n## Phases / sub-issues\n\n- [ ] #176 — Declare `output_schema` on the three compound tools (phase 1, zero schema conflict)\n- [ ] #177 — Refactor `maybe", "SourceUrl": "https://github.com/AutomoxCommunity/automox-mcp/issues/183", "PublishedAt": "2026-06-08T00:07:54.000Z", "State": "closed", "Comments": 1, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "MCP App: access certification (RBAC) review", "Excerpt": "## Problem / why\n\nAn interactive surface to review users / roles / permissions and **certify** (or flag) access — a periodic security-hygiene task that benefits from an inline, reviewable UI rather than stitching together several read calls.\n\n## Scope\n\n- Read-first review of RBAC state with optional **gated** changes (correct destructive tier per `docs/api-coverage.md`).\n- Builds on the read-only triage App pattern and the structured-output schema.\n- Graceful degradation to the existing tool pat", "SourceUrl": "https://github.com/AutomoxCommunity/automox-mcp/issues/182", "PublishedAt": "2026-06-08T00:07:05.000Z", "State": "closed", "Comments": 0, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "MCP App: remediation-apply review (gated operation)", "Excerpt": "## Problem / why\n\nRemediation-apply is among the most consequential operations the server exposes. The destructive-gating policy (`docs/api-coverage.md`) asks for a mitigation/confirmation on operations at this tier — and an **interactive review UI *is* that mitigation**: the operator sees exactly what will be applied before confirming. This flow gets the most design care of the App set.\n\n## Scope\n\n- App review surface for remediation-apply, wired to the highest destructive tier's confirmation r", "SourceUrl": "https://github.com/AutomoxCommunity/automox-mcp/issues/181", "PublishedAt": "2026-06-08T00:07:02.000Z", "State": "closed", "Comments": 0, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "MCP App: policy change + blast-radius review", "Excerpt": "## Problem / why\n\nPolicy edits can affect many devices. An interactive review that shows the **blast radius** — which/how many devices a proposed change would touch — *before* applying is a meaningful safety and UX improvement over a bare write call.\n\n## Scope\n\n- App surface that previews the affected device set for a proposed policy change, then gates the apply (correct destructive tier per `docs/api-coverage.md`).\n- Builds on the read-only triage App pattern and the structured-output schema.\n-", "SourceUrl": "https://github.com/AutomoxCommunity/automox-mcp/issues/180", "PublishedAt": "2026-06-08T00:06:57.000Z", "State": "closed", "Comments": 0, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "MCP App: patch-approval review flow (flagship write-App)", "Excerpt": "## Problem / why\n\nThe flagship interactive flow: surface pending/available patches and let an operator **review-and-approve inside the App** instead of issuing a blind write call. The review UI becomes an inline, reviewable confirmation step before a consequential write.\n\n## Scope\n\n- Builds on the dependency-free App pattern from the read-only triage pilot, and on the structured-output schema work.\n- Adds an `@app.tool()` backend write action, gated by the existing **destructive-gating tiers** —", "SourceUrl": "https://github.com/AutomoxCommunity/automox-mcp/issues/179", "PublishedAt": "2026-06-08T00:06:53.000Z", "State": "closed", "Comments": 0, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "MCP App (read-only): non-compliant triage surface on get_compliance_snapshot", "Excerpt": "## Problem / why\n\nThe MCP **Apps** extension lets a tool ship an interactive UI (a `ui://` HTML resource + `AppConfig`) that hosts render inline, degrading gracefully to the structured payload on non-Apps hosts. A read-only **non-compliant triage** surface gives an at-a-glance, interactive view (non-compliant devices, stale devices, policy summary) the model can pull up — a useful complement to plain tool output. Starting read-only keeps it safe and dependency-light, and establishes the App patt", "SourceUrl": "https://github.com/AutomoxCommunity/automox-mcp/issues/178", "PublishedAt": "2026-06-08T00:06:48.000Z", "State": "closed", "Comments": 0, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Refactor maybe_format_markdown to ToolResult so read tools can advertise outputSchema (phase 2)", "Excerpt": "## Problem / why\n\nExtending `outputSchema` to the read/report tools is blocked by `maybe_format_markdown` (`src/automox_mcp/utils/tooling.py`): in markdown mode it rewrites `data` into a markdown **string**, which can't satisfy a fixed object schema. So today we can't advertise an object schema while also returning markdown.\n\n## Approach\n\nRefactor `maybe_format_markdown` to return a FastMCP `ToolResult(content=, structured_content=)`:\n\n- the structured object is preserved fo", "SourceUrl": "https://github.com/AutomoxCommunity/automox-mcp/issues/177", "PublishedAt": "2026-06-08T00:06:39.000Z", "State": "closed", "Comments": 0, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Declare outputSchema (structured content) on the compound tools", "Excerpt": "## Problem / why\n\nMCP lets a tool advertise an `outputSchema` so schema-aware clients can validate results and render them richly. Our tools already return a `{\"data\", \"metadata\"}` envelope that FastMCP attaches as `structuredContent`, but we never *advertise* a schema — so clients can't rely on the shape. Declaring it improves client-side validation, enables typed rendering, and is the foundation App surfaces consume.\n\n## Scope — phase 1 (zero schema conflict)\n\nAdd explicit `output_schema=