@decionis/mcp 0.2.0 → 0.3.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/README.md +24 -2
- package/dist/AgentHookCli.js +2 -2
- package/dist/ManagedAgentHookCli.js +328 -194
- package/dist/agent/AgentIndex.js +2 -2
- package/dist/{chunk-7QNV7MXC.js → chunk-ABHNQFWI.js} +2 -2
- package/dist/{chunk-NF5JL6QR.js → chunk-LIVLO4MV.js} +329 -195
- package/dist/chunk-LIVLO4MV.js.map +1 -0
- package/dist/index.js +312 -52
- package/dist/index.js.map +1 -1
- package/package.json +4 -4
- package/dist/chunk-NF5JL6QR.js.map +0 -1
- /package/dist/{chunk-7QNV7MXC.js.map → chunk-ABHNQFWI.js.map} +0 -0
package/README.md
CHANGED
|
@@ -62,8 +62,30 @@ and re-evaluates. The handlers are the hosted MCP's own, bound to the in-process
|
|
|
62
62
|
the local loop is the hosted loop. Both call `presence.decionis.com` (`openWorldHint:
|
|
63
63
|
true`). Production enforcement is sales-assisted.
|
|
64
64
|
|
|
65
|
-
|
|
66
|
-
|
|
65
|
+
### Shield — the user's own spending rules (consumer)
|
|
66
|
+
|
|
67
|
+
The `shield.*` tools ask a person's Decionis Shield before an assistant
|
|
68
|
+
spends their money: `shield.request_purchase` returns ALLOW, ASK or BLOCK
|
|
69
|
+
against the limits the person set in the Shield app, with a signed Dispute
|
|
70
|
+
Passport behind every hold. Two ways to bind:
|
|
71
|
+
|
|
72
|
+
- **Pair from the app (ten minutes, no keys).** In the Shield app, open *AI
|
|
73
|
+
spending allowance → Bind your own agent*; it shows a six-character code.
|
|
74
|
+
Tell your assistant *"pair with Shield, code ABC123"* — it calls
|
|
75
|
+
`shield.pair`, which claims the code and keeps the production credential in
|
|
76
|
+
`~/.decionis/shield-credential.json` (`0600`; `DECIONIS_SHIELD_CREDENTIAL_FILE`
|
|
77
|
+
moves it). The app then lists the assistant with what it was allowed to
|
|
78
|
+
spend this week, and can revoke it. Pairing again from the same computer
|
|
79
|
+
rotates the credential rather than binding a second agent.
|
|
80
|
+
- **Configure a key (integrators).** `DECIONIS_SHIELD_API_KEY` and
|
|
81
|
+
`DECIONIS_SHIELD_APP_ID` from `POST /v1/consumer/shield/integrations` win
|
|
82
|
+
over the paired file. `DECIONIS_SHIELD_API_URL` defaults to
|
|
83
|
+
`https://api.shield.decionis.com`.
|
|
84
|
+
|
|
85
|
+
The six tools are always advertised. Until the server is paired or configured,
|
|
86
|
+
every `shield.*` call fails closed with `SHIELD_MCP_CONFIGURATION_REQUIRED`
|
|
87
|
+
and tells the model to ask the user for the code — an error is never
|
|
88
|
+
permission to execute.
|
|
67
89
|
|
|
68
90
|
### Kubernetes execution-authority tools
|
|
69
91
|
|
package/dist/AgentHookCli.js
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
#!/usr/bin/env node
|
|
2
2
|
import {
|
|
3
3
|
AgentHookCommand
|
|
4
|
-
} from "./chunk-
|
|
5
|
-
import "./chunk-
|
|
4
|
+
} from "./chunk-ABHNQFWI.js";
|
|
5
|
+
import "./chunk-LIVLO4MV.js";
|
|
6
6
|
|
|
7
7
|
// src/AgentHookCli.ts
|
|
8
8
|
void AgentHookCommand.run(process.argv.slice(2)).then((exitCode) => {
|