跳到主要內容Skip to content
中EN
選單Menu
概念作品Concept

AIAI製造與企業資安Manufacturing and enterprise security

AI 代理權限與稽核儀表板AI agent permissions and audit dashboard

為虛構的製造商「立岩」設計的 AI 代理控管台概念:集中呈現待核准的動作、每一次工具呼叫、技能審查狀態與異常警示,並以權限矩陣和事件應變清單管理多個代理。

An AI agent console concept for Liyan, a fictional manufacturer: one place for actions awaiting approval, every tool call, skill review status and anomaly alerts, with a permission matrix and an incident-response checklist for several agents.

此為概念設計,用於展示我們的設計與開發能力,並非真實客戶案例。

This is a concept design that demonstrates our design and development capabilities; it is not a real client project.

Concept: AI agent console showing a risk-sorted approval queue, the tool-call log, skill review status, and alerts for a blocked prompt injection and unusual call volume

公司導入的 AI 代理一多,客服、業務、採購各有一個,很快就沒人說得清楚:哪個代理能讀哪些資料、能不能寄信或改單、昨天到底做了哪些事。一旦有人在郵件或文件裡藏了指令,試圖讓代理做出原本不該做的事,也很難第一時間發現。

這個概念把所有代理的動作集中到一個控管台:待核准動作依風險排序,高風險動作需兩人核准;工具呼叫紀錄附上時間、權限等級與結果;異常警示會標出被攔截的提示注入嘗試與不尋常的呼叫量。政策頁以「代理 × 工具」矩陣設定唯讀、需核准或禁止,並附上事件發生時逐步執行的應變清單。

實際開發時,我們會在代理與公司系統之間放一層閘道,所有工具呼叫都經過 MCP 伺服器與權限檢查,每個代理使用獨立的服務帳號與最小權限,憑證定期輪替;代理在隔離環境中執行,外部內容一律視為不可信,紀錄集中保存供稽核。控管台中的數字與事件皆為示意資料。

Once a company runs several AI agents, one each for customer service, sales and purchasing, nobody can say for sure which agent can read what, whether it can send email or change orders, or what it actually did yesterday. And when someone hides instructions in an email or document to make an agent do something it should not, it is hard to notice in time.

This concept brings every agent’s actions into one console. Actions awaiting approval are sorted by risk, and high-risk ones need two approvers; the tool-call log shows time, permission level and outcome; anomaly alerts flag blocked prompt-injection attempts and unusual call volumes. A policy page sets read-only, approval-required or blocked for each agent-and-tool pair, alongside a step-by-step checklist for responding to an incident.

In a real build we would put a gateway between the agents and company systems, so every tool call passes through MCP servers and a permission check. Each agent gets its own service account with least privilege and rotated credentials, runs in an isolated environment, treats all outside content as untrusted, and has its logs kept centrally for audit. Figures and incidents in the console are illustrative.

有類似的需求?Planning something similar?

先聊 30 分鐘:你的目標、預算與時程,我們免費提供初步建議。

Start with a free 30-minute call about your goals, budget and timeline.

預約免費 30 分鐘諮詢Book a free 30-minute consultation