@gethelio/proxy 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +201 -0
- package/README.md +311 -0
- package/dist/cli.js +6420 -0
- package/dist/dashboard-assets/assets/index-DG3h7Cvn.css +1 -0
- package/dist/dashboard-assets/assets/index-Yyo92yXC.js +128 -0
- package/dist/dashboard-assets/favicon.svg +16 -0
- package/dist/dashboard-assets/index.html +15 -0
- package/dist/dashboard-assets/logo.svg +16 -0
- package/dist/index.d.ts +1874 -0
- package/dist/index.js +5672 -0
- package/package.json +69 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,311 @@
|
|
|
1
|
+
<p align="center">
|
|
2
|
+
<h1 align="center">Helio</h1>
|
|
3
|
+
<p align="center">Open-source governance proxy for AI agents</p>
|
|
4
|
+
</p>
|
|
5
|
+
|
|
6
|
+
<p align="center">
|
|
7
|
+
<a href="https://github.com/gethelio/helio/actions/workflows/ci.yml"><img src="https://github.com/gethelio/helio/actions/workflows/ci.yml/badge.svg" alt="CI" /></a>
|
|
8
|
+
<a href="https://github.com/gethelio/helio/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-Apache%202.0-blue.svg" alt="License" /></a>
|
|
9
|
+
<a href="https://www.npmjs.com/package/@gethelio/proxy"><img src="https://img.shields.io/npm/v/@gethelio/proxy.svg" alt="npm version" /></a>
|
|
10
|
+
</p>
|
|
11
|
+
|
|
12
|
+
<p align="center">
|
|
13
|
+
<a href="https://github.com/gethelio/helio/blob/main/docs/getting-started.md">Getting Started</a> · <a href="https://github.com/gethelio/helio/blob/main/docs/configuration.md">Docs</a> · <a href="https://github.com/gethelio/helio/blob/main/CONTRIBUTING.md">Contributing</a>
|
|
14
|
+
</p>
|
|
15
|
+
|
|
16
|
+
---
|
|
17
|
+
|
|
18
|
+
Helio is an MCP proxy that sits between your AI agents and the tools they use. Every tool call passes through Helio, which enforces policies, checks evidence, routes approvals, tracks spend, and records everything - **without changing your agent code or your MCP servers.**
|
|
19
|
+
|
|
20
|
+
```bash
|
|
21
|
+
npx @gethelio/proxy init
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
## Why Helio?
|
|
25
|
+
|
|
26
|
+
Your agent just called an API you didn't expect. It spent money you didn't authorize. It modified a production record you can't easily undo.
|
|
27
|
+
|
|
28
|
+
Model providers are building governance for their own platforms but your agents run across Claude, ChatGPT, LangChain, CrewAI, and custom frameworks. No single platform governs the full picture. And none of them govern what happens in downstream systems like Stripe, Salesforce, or GitHub.
|
|
29
|
+
|
|
30
|
+
Helio governs what agents **do to the rest of the world** across any MCP-compatible agent, any tool, any platform.
|
|
31
|
+
|
|
32
|
+
## How It Works
|
|
33
|
+
|
|
34
|
+
```
|
|
35
|
+
┌──────────────┐ ┌──────────────────────┐ ┌──────────────┐
|
|
36
|
+
│ │ │ Helio │ │ │
|
|
37
|
+
│ MCP Client │────▶│ │────▶│ MCP Server │
|
|
38
|
+
│ (Agent) │◀────│ • Policy engine │◀────│ (Tools) │
|
|
39
|
+
│ │ │ • Evidence grounding │ │ │
|
|
40
|
+
└──────────────┘ │ • Approval workflows │ └──────────────┘
|
|
41
|
+
│ • Rate & spend limits │
|
|
42
|
+
Optional │ • Audit trail │
|
|
43
|
+
┌─────────┐ │ • Self-repair feedback│
|
|
44
|
+
│ SDK │───▶│ │
|
|
45
|
+
│ (thin) │ └──────────────────────┘
|
|
46
|
+
└─────────┘
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
Two integration paths:
|
|
50
|
+
|
|
51
|
+
1. **Proxy only**: Point your MCP client at Helio instead of your MCP server. Zero code changes. Immediate governance.
|
|
52
|
+
2. **Proxy + SDK**: Add the thin Python SDK to annotate tool calls with evidence context and action dependencies. Richer governance, under 500 lines of code.
|
|
53
|
+
|
|
54
|
+
## Quick Start (5 minutes)
|
|
55
|
+
|
|
56
|
+
### 1. Install
|
|
57
|
+
|
|
58
|
+
```bash
|
|
59
|
+
npx @gethelio/proxy init
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
### 2. Configure
|
|
63
|
+
|
|
64
|
+
Create a `helio.yaml` in your project root:
|
|
65
|
+
|
|
66
|
+
```yaml
|
|
67
|
+
version: '1'
|
|
68
|
+
|
|
69
|
+
upstream:
|
|
70
|
+
url: 'http://localhost:3001/mcp' # Your existing MCP server
|
|
71
|
+
|
|
72
|
+
listen:
|
|
73
|
+
port: 3000 # Helio listens here
|
|
74
|
+
|
|
75
|
+
policies:
|
|
76
|
+
default: allow
|
|
77
|
+
|
|
78
|
+
rules:
|
|
79
|
+
# Require approval for write operations
|
|
80
|
+
- match:
|
|
81
|
+
tool: '*'
|
|
82
|
+
annotations:
|
|
83
|
+
readOnlyHint: false
|
|
84
|
+
action: require_approval
|
|
85
|
+
approval:
|
|
86
|
+
channel: dashboard
|
|
87
|
+
timeout: 300s
|
|
88
|
+
|
|
89
|
+
# Block destructive operations
|
|
90
|
+
- match:
|
|
91
|
+
tool: 'delete_*'
|
|
92
|
+
action: deny
|
|
93
|
+
feedback:
|
|
94
|
+
message: 'Destructive operations are disabled'
|
|
95
|
+
|
|
96
|
+
# Rate limit expensive API calls
|
|
97
|
+
- match:
|
|
98
|
+
tool: 'search_*'
|
|
99
|
+
action: rate_limit
|
|
100
|
+
limits:
|
|
101
|
+
max_calls: 100
|
|
102
|
+
window: 1h
|
|
103
|
+
key: tool
|
|
104
|
+
|
|
105
|
+
# Spend limit on payment tools
|
|
106
|
+
- match:
|
|
107
|
+
tool: 'create_payment'
|
|
108
|
+
action: spend_limit
|
|
109
|
+
limits:
|
|
110
|
+
max_spend:
|
|
111
|
+
field: '$.amount'
|
|
112
|
+
limit: 5000
|
|
113
|
+
currency: 'GBP'
|
|
114
|
+
window: 24h
|
|
115
|
+
|
|
116
|
+
audit:
|
|
117
|
+
storage: sqlite
|
|
118
|
+
retention: 90d
|
|
119
|
+
include_responses: true
|
|
120
|
+
|
|
121
|
+
dashboard:
|
|
122
|
+
enabled: true
|
|
123
|
+
port: 3100
|
|
124
|
+
# Required whenever any rule uses `require_approval`. Generate with:
|
|
125
|
+
# openssl rand -hex 32
|
|
126
|
+
api_secret: '${HELIO_DASHBOARD_SECRET}'
|
|
127
|
+
```
|
|
128
|
+
|
|
129
|
+
If you use the `${HELIO_DASHBOARD_SECRET}` placeholder above, set it before `start`:
|
|
130
|
+
|
|
131
|
+
```bash
|
|
132
|
+
export HELIO_DASHBOARD_SECRET="$(openssl rand -hex 32)"
|
|
133
|
+
```
|
|
134
|
+
|
|
135
|
+
> **Host binding defaults.** `helio start` binds `listen.host` and `dashboard.host` to `127.0.0.1` by default (the `helio init` template writes this value, and the schema defaults to it). Do **not** flip either to `0.0.0.0` without putting an authenticating reverse proxy in front — the MCP edge has no authentication at all, and the dashboard sideband's bearer is a shared secret, not a user session. The [Docker quickstart](https://github.com/gethelio/helio/tree/main/docker) inverts this layering: inside the container the bundled config binds `0.0.0.0` (correct for the container's virtual network) and Compose's `ports:` map publishes both ports back to `127.0.0.1` on the host.
|
|
136
|
+
|
|
137
|
+
### 3. Start Helio
|
|
138
|
+
|
|
139
|
+
```bash
|
|
140
|
+
npx @gethelio/proxy start
|
|
141
|
+
```
|
|
142
|
+
|
|
143
|
+
### 4. Point your agent at Helio
|
|
144
|
+
|
|
145
|
+
```json
|
|
146
|
+
{
|
|
147
|
+
"mcpServers": {
|
|
148
|
+
"my-tools": {
|
|
149
|
+
"url": "http://localhost:3000/mcp"
|
|
150
|
+
}
|
|
151
|
+
}
|
|
152
|
+
}
|
|
153
|
+
```
|
|
154
|
+
|
|
155
|
+
### 5. Open the dashboard
|
|
156
|
+
|
|
157
|
+
```
|
|
158
|
+
http://localhost:3100
|
|
159
|
+
```
|
|
160
|
+
|
|
161
|
+
That's it. Every tool call now passes through Helio. This includes full audit trail, approval workflows, rate limits, and spend controls.
|
|
162
|
+
|
|
163
|
+
> **Notification transport semantics (v0.1).** For JSON-RPC notifications (requests with no `id`), Helio's `streamable-http` endpoint returns `HTTP 202 Accepted` with an empty body after forwarding upstream fire-and-forget. For the legacy `sse` transport, POST requests also return `202` with empty body and response payloads are delivered on the SSE stream. For correlated (non-notification) requests, Helio now requires upstream JSON-RPC responses to include an `id`; missing-id upstream replies are wrapped as protocol-invalid upstream errors.
|
|
164
|
+
|
|
165
|
+
## Features
|
|
166
|
+
|
|
167
|
+
### Policy Engine
|
|
168
|
+
|
|
169
|
+
Declarative YAML rules that match on tool name, annotations, input parameters, environment, and cumulative state. Policies hot-reload without restart.
|
|
170
|
+
|
|
171
|
+
```yaml
|
|
172
|
+
rules:
|
|
173
|
+
- match:
|
|
174
|
+
tool: 'create_payment'
|
|
175
|
+
input:
|
|
176
|
+
'$.amount': { gt: 1000 }
|
|
177
|
+
action: require_approval
|
|
178
|
+
```
|
|
179
|
+
|
|
180
|
+
### Evidence Grounding
|
|
181
|
+
|
|
182
|
+
Require proof before high-stakes actions. A refund requires a prior order lookup. A deployment requires a passing test run. The optional SDK marks tool outputs as evidence; the proxy enforces evidence requirements.
|
|
183
|
+
|
|
184
|
+
```yaml
|
|
185
|
+
rules:
|
|
186
|
+
- match:
|
|
187
|
+
tool: 'process_refund'
|
|
188
|
+
action: deny
|
|
189
|
+
evidence:
|
|
190
|
+
requires: ['orders.lookup']
|
|
191
|
+
```
|
|
192
|
+
|
|
193
|
+
```python
|
|
194
|
+
# Optional SDK enrichment
|
|
195
|
+
from helio import HelioContext
|
|
196
|
+
|
|
197
|
+
# Mark a tool output as evidence
|
|
198
|
+
with HelioContext() as ctx:
|
|
199
|
+
result = orders.lookup(order_id)
|
|
200
|
+
ctx.mark_evidence("orders.lookup", "order_data", result)
|
|
201
|
+
```
|
|
202
|
+
|
|
203
|
+
The SDK talks to the proxy over the sideband API (default `127.0.0.1:3200`; bind host is configurable via `sdk.host`). On every `helio start` the proxy generates a fresh 32-byte hex token and prints it to stderr:
|
|
204
|
+
|
|
205
|
+
```
|
|
206
|
+
SDK sideband listening on http://127.0.0.1:3200
|
|
207
|
+
SDK token (pass as HELIO_SDK_TOKEN env var to your SDK clients):
|
|
208
|
+
3f9c2b...d8a1
|
|
209
|
+
```
|
|
210
|
+
|
|
211
|
+
Pass the same value to the SDK process via `HELIO_SDK_TOKEN` and the SDK automatically attaches `Authorization: Bearer <token>` to every sideband call. The sideband also rejects any request carrying a non-null `Origin` header, so a malicious local HTML file cannot talk to it through a browser. Operators who need a stable token across restarts can set `HELIO_SDK_TOKEN` explicitly in the proxy's environment — the proxy respects a pre-set value instead of regenerating one.
|
|
212
|
+
|
|
213
|
+
### Self-Repair Feedback
|
|
214
|
+
|
|
215
|
+
When Helio blocks an action, it returns structured feedback explaining what failed and what the agent should do next. The agents can then self-correct and retry.
|
|
216
|
+
|
|
217
|
+
```json
|
|
218
|
+
{
|
|
219
|
+
"blocked": true,
|
|
220
|
+
"reason": "evidence_missing",
|
|
221
|
+
"missing_evidence": ["orders.lookup"],
|
|
222
|
+
"suggestion": "Call orders.lookup with the order ID before retrying"
|
|
223
|
+
}
|
|
224
|
+
```
|
|
225
|
+
|
|
226
|
+
### Action Dependency Chains
|
|
227
|
+
|
|
228
|
+
Declare prerequisite actions in policy. The proxy tracks completed actions per session and blocks anything where prerequisites aren't met.
|
|
229
|
+
|
|
230
|
+
```yaml
|
|
231
|
+
rules:
|
|
232
|
+
- match:
|
|
233
|
+
tool: 'process_refund'
|
|
234
|
+
requires: ['orders.lookup', 'customer.verify']
|
|
235
|
+
```
|
|
236
|
+
|
|
237
|
+
### Approval Workflows
|
|
238
|
+
|
|
239
|
+
Route sensitive actions to Slack, webhook, or the Helio dashboard. Configurable timeout and escalation, plus a dashboard-only break-glass override (REST API and dashboard UI; not exposed as a Slack button).
|
|
240
|
+
If a channel delivery fails, Helio logs an operational warning and emits an `approval_notification_failed` dashboard event so operators can investigate without losing the underlying pending ticket.
|
|
241
|
+
|
|
242
|
+
### Transaction Controls
|
|
243
|
+
|
|
244
|
+
Rate limits per tool and per session. Spend limits with cumulative tracking. Irreversible action detection. Dry-run mode that executes the full pipeline without forwarding to the MCP server.
|
|
245
|
+
|
|
246
|
+
### Audit Trail
|
|
247
|
+
|
|
248
|
+
Every tool call recorded: timestamp, agent identity, tool name, inputs, policy decision, evidence chain, approval status, downstream response, and latency. Searchable dashboard. Export to JSON or CSV.
|
|
249
|
+
|
|
250
|
+
## How Helio Compares
|
|
251
|
+
|
|
252
|
+
| | Helio | Guild.ai | JetStream | Cerbos | Salus |
|
|
253
|
+
| ----------------------------------- | --------------------- | ----------------- | --------------- | --------------- | -------------- |
|
|
254
|
+
| **Approach** | Proxy + thin SDK | Platform runtime | Enterprise SaaS | Sidecar library | In-process SDK |
|
|
255
|
+
| **Requires migration** | No | Yes | No | No | Code changes |
|
|
256
|
+
| **Time to value** | 5 minutes | Weeks | Weeks | Hours | Minutes |
|
|
257
|
+
| **Open source** | ✅ Apache 2.0 | ❌ | ❌ | ✅ Apache 2.0 | ❌ |
|
|
258
|
+
| **Evidence grounding** | ✅ | ❌ | ❌ | ❌ | ✅ |
|
|
259
|
+
| **Self-repair feedback** | ✅ | ❌ | ❌ | ❌ | ✅ |
|
|
260
|
+
| **Approval workflows** | ✅ | ✅ (in runtime) | ✅ | ❌ | ❌ |
|
|
261
|
+
| **Transaction controls** | ✅ \* | Basic | Cost tracking | ❌ | ❌ |
|
|
262
|
+
| **Audit trail** | ✅ (incl. downstream) | ✅ (runtime only) | ✅ | Decision logs | ❌ |
|
|
263
|
+
| **Cross-platform** | ✅ Any MCP agent | ❌ Guild only | ✅ | ✅ | ✅ Python only |
|
|
264
|
+
| **Governs agents you didn't build** | ✅ | ❌ | ✅ | ✅ | ❌ |
|
|
265
|
+
| **Language agnostic** | ✅ (proxy) | ✅ | ✅ | ✅ | ❌ Python only |
|
|
266
|
+
|
|
267
|
+
\* Per-tool and per-session spend limits ship in v0.1. Cross-tool spend aggregation is planned for v0.2.
|
|
268
|
+
|
|
269
|
+
## Works With
|
|
270
|
+
|
|
271
|
+
Helio works with any MCP-compatible agent or framework:
|
|
272
|
+
|
|
273
|
+
- **Claude** (Anthropic)
|
|
274
|
+
- **ChatGPT** (OpenAI)
|
|
275
|
+
- **LangChain / LangGraph**
|
|
276
|
+
- **CrewAI**
|
|
277
|
+
- **AutoGen**
|
|
278
|
+
- **Custom agents** using any MCP client SDK
|
|
279
|
+
|
|
280
|
+
## Documentation
|
|
281
|
+
|
|
282
|
+
The full docs live in the [monorepo](https://github.com/gethelio/helio) and are not bundled into this package tarball.
|
|
283
|
+
|
|
284
|
+
- **[Getting Started](https://github.com/gethelio/helio/blob/main/docs/getting-started.md)**: Install and configure in 5 minutes
|
|
285
|
+
- **[Configuration Reference](https://github.com/gethelio/helio/blob/main/docs/configuration.md)**: Every YAML option explained
|
|
286
|
+
- **[Policy Guide](https://github.com/gethelio/helio/blob/main/docs/policies.md)**: How to write rules with examples
|
|
287
|
+
- **[Approval Workflows](https://github.com/gethelio/helio/blob/main/docs/approvals.md)**: Slack, webhook, and dashboard approvals
|
|
288
|
+
- **[Audit Trail](https://github.com/gethelio/helio/blob/main/docs/audit.md)**: What's recorded, how to search, how to export
|
|
289
|
+
|
|
290
|
+
## Examples
|
|
291
|
+
|
|
292
|
+
Ready-made configurations for common patterns:
|
|
293
|
+
|
|
294
|
+
- **[Basic](https://github.com/gethelio/helio/tree/main/examples/basic)**: Deny destructive operations, allow everything else
|
|
295
|
+
- **[Slack Approvals](https://github.com/gethelio/helio/tree/main/examples/slack-approvals)**: Route destructive actions to Slack
|
|
296
|
+
- **[Spend Limits](https://github.com/gethelio/helio/tree/main/examples/spend-limits)**: Govern payment tool usage
|
|
297
|
+
|
|
298
|
+
## Contributing
|
|
299
|
+
|
|
300
|
+
We welcome contributions. See [CONTRIBUTING.md](https://github.com/gethelio/helio/blob/main/CONTRIBUTING.md) for setup instructions, coding standards, and PR process.
|
|
301
|
+
|
|
302
|
+
Good first issues are labeled [`good-first-issue`](https://github.com/gethelio/helio/labels/good-first-issue).
|
|
303
|
+
|
|
304
|
+
## Community
|
|
305
|
+
|
|
306
|
+
- **[GitHub Issues](https://github.com/gethelio/helio/issues)**: Bug reports and feature requests
|
|
307
|
+
- **[Twitter/X](https://x.com/get_helio)**: Updates and announcements
|
|
308
|
+
|
|
309
|
+
## License
|
|
310
|
+
|
|
311
|
+
Apache 2.0 - see [LICENSE](./LICENSE).
|