The operating problem
Direct model-to-tool connectivity can bypass API ownership, tenant isolation, data classification, change control, and human approval.
The intended control surface
This capability is part of the reviewed product architecture, not a decorative console module.
- MCP server and tool registry
- Authentication and tenant-scoped authorization
- Argument and result validation
- Read-only, dry-run, and approval modes
What exists today
No MCP runtime capability exists yet. The page documents a design-partner direction only.
Work with the implementation team
Reallexi is accepting architecture conversations with teams whose requirements can shape this production slice. An inquiry does not imply that an unshipped feature is available.
Frequently asked questions
Is this capability generally available?
No. The page describes a reviewed implementation direction. The current capability boundary is stated above and in the public changelog.
Can Reallexi evaluate our requirements?
Yes. Use the enterprise inquiry form without including credentials, private payloads, or regulated data.