{"slug":"strategy/business-strategy/10_CUSTOMER_ZERO_MCP_POOL_UI","title":"10 — Customer Zero MCP Pool UI","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/business-strategy/10_CUSTOMER_ZERO_MCP_POOL_UI.mdx","bytes":1424,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Restricted Customer Zero operator handoff\n\n## Scope\n\nThis is an internal operational projection for authorized IntegrateWise\nCustomer Zero/Platform operators. It is not the public MCP product surface and\nis not automatically available to customer-production tenants.\n\n## Required views\n\n- registered servers/tools and version;\n- health, latency, failure rate and last probe;\n- tenant/user allowlists and deny reasons;\n- resolver route and fallback state;\n- authorization binding and credential-reference health;\n- invocation/audit trace with redacted arguments;\n- quarantine, disable and version-promotion controls.\n\nThe internal pool may contain 55 registered capabilities. The published **IW\nSpine Tools** MCP remains exactly 19 semantic tools. The UI must always label\nwhich boundary is being viewed.\n\n## Control rules\n\n- Reads require Customer Zero operator RBAC.\n- Any route/policy/version mutation creates a governance proposal.\n- Credential material is never rendered.\n- Invocation replay uses a new trace and idempotency context.\n- Disabled or unhealthy tools cannot be advertised as available capabilities.\n\n## Environment rule\n\nDevelopment, Customer Zero and Customer Production registries, credentials,\nqueues, operational state and audit streams are isolated. Configuration may be\npromoted as a versioned artifact; runtime data and memory never move between\nthem.\n"}