TL;DR: MCP Apps extends the protocol into interactive interfaces so enterprise AI agents can use structured forms, dashboards, and approval views instead of forcing complex workflows through chat, according to Willow. Identity and access teams now have to govern UI resources, approvals, and the tool calls they trigger.
Editorial analysis by NHI Mgmt Group, based on content published by Willow: “MCP Apps Extension: Why Interactive UI Matters for Enterprise AI Agents”.
Key questions
Q: Why do interactive agent interfaces create new governance risk?
A: They shift decision-making into a richer surface where defaults, field order, and prompts can influence outcomes before policy is applied.
Q: What should teams do first when an agent can initiate UI-based actions?
A: Start by inventorying which workflows can trigger tool calls from the interface itself.
Q: How should security teams govern interactive UI inside AI agent workflows?
A: Security teams should govern interactive UI as part of the agent’s execution path, not as a separate front end.
Practitioner guidance
- Review UI resources before allowing execution Assess declared ui:// resources as part of pre-production control review, including what the interface can display, request, and trigger.
- Bind approvals to the presented interface Require approval records to capture the exact UI resource, the decision made, and the downstream tool call so auditors can reconstruct the path.
- Separate rendering from execution authority Ensure sandboxed iframes cannot silently expand privilege and that any UI-initiated tool call requires explicit policy evaluation.
Bottom line: MCP Apps extends the protocol into interactive interfaces, which means governance now has to cover UI resources, approvals, and the resulting tool calls.
Glossary terms: Interactive UI Resource, App-Initiated Tool Call, Delegated Authority Model, Approval Workflow
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Interactive UI becomes part of the authorisation plane: MCP Apps does not merely improve presentation for AI agents. It moves policy-relevant decisions into a richer control surface where approvals, defaults, and action triggers can influence what gets executed. For identity governance, that means the reviewed object is no longer just the tool call. The UI resource, the host, and the approval pathway all become part of the trust model, and practitioners need to treat them as such.
A few things that frame the scale:
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the difference between a chat-based agent workflow and an interactive UI workflow?
A: A chat workflow relies on linear text exchanges, while an interactive UI workflow uses structured fields, dashboards, and approval surfaces to present state and trigger actions. The latter can improve comprehension, but it also introduces another control layer that must be reviewed, logged, and bound to the right identity and permission scope.
👉 Read our full editorial: MCP Apps changes how enterprise agents handle complex workflows