AGNTCon + MCPCon Japan 2026

Open protocols like MCP and A2A let you combine agents and tools from different teams into one system.

But at company-wide scale, new challenges arise: who can access the system, who can call which agent, whether it fails safely, and whether it follows internal governance. Coding agents now write most of the code, so the spec we give them shapes the whole system's quality.

We'll share how we tackled this from two sides on a company-wide MCP × A2A platform.

Architecture side: where to declare per-agent access, how to handle attribute-based authorization, how to split the write and read sides of authorization data, and how to stay fail-closed, mapped to standard authorization-control models.

Development-process side: a multi-stage review of the requirements given to coding agents, covering format, clarity, cross-walk with external standards, and adversarial testing. This catches auth and governance issues, plus input validation flaws and data leakage, before code is written.

You'll come away with ideas for an interoperable MCP/A2A authorization layer, a reusable way to gather enterprise-grade requirements, and a view of specs themselves as security assets.

___________________________
Presentation Language: Japanese

Captioning will be available for attendees in 50+ languages through Wordly. See instructions in each room to utilize captioning.