@apono-io/apono-mcp 0.2.53-beta.4 → 0.2.53-beta.6
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 +2 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -8,10 +8,11 @@ Just-in-time access to your infrastructure and SaaS tools for AI agents, governe
|
|
|
8
8
|
- **Trust policies on every call.** Each tool call is classified by intent (read, write, delete, ...) and allowed, denied, or sent to a human for approval.
|
|
9
9
|
- **One server, many targets.** Databases, cloud accounts, Kubernetes and SaaS tools that your Apono admin connected, all behind one MCP server.
|
|
10
10
|
|
|
11
|
-
## What's new in v0.2.53-beta.
|
|
11
|
+
## What's new in v0.2.53-beta.6 (since v0.2.52)
|
|
12
12
|
|
|
13
13
|
### 🛡️ Reliability
|
|
14
14
|
- **A session that lost its credential now recovers from a credential another session already refreshed** - When one session refreshed a rejected credential, other sessions of the same user kept the old one and failed every call until they restarted. A session now picks up the refreshed credential and retries the call.
|
|
15
|
+
- **A gateway that cannot start a tool server no longer rotates credentials other sessions are using** - When a managed tool server failed to start, usually because its command was missing on the machine, the gateway treated the failure as a rejected credential and rotated it. Other sessions of the same user then lost access until they restarted. The gateway now leaves the credential alone when the failure happened before the tool server used it.
|
|
15
16
|
|
|
16
17
|
## Requirements
|
|
17
18
|
|