Controlled execution
Helix MCP Gateway
Capability within policy.
Helix MCP Gateway places explicit policy, limits, review and audit between an authorised MCP client and each Helix environment.
One bounded action passes through policy and review.
Core capabilities
Useful by design.
Bounded by design.
- 01Explicit DEV, QA or PROD selection
- 02Bounded form discovery, field metadata and reads
- 03Reviewed, read-only SQL through AR API
- 04Two-phase creation and update workflows
- 05Independent environment policies
- 06Sanitised audit and operational evidence
Design principles
Never infer the target
Every external operation names its environment; there is no conversational or implicit default.
Plan before apply
Sensitive operations are proposed, displayed for review and applied only after explicit approval.
Narrow, never expand
Local policy can reduce the configured Helix account's access, but it cannot grant additional permissions.
Product boundary
Gateway does not provide deletion, bulk writes, direct database connections, permission elevation or unattended production automation.
Demos
Observe, review and stay inside policy.
See how documentary context and a separate, human-approved Gateway validation supported one synthetic DEV update.
Next step