@apono-io/apono-mcp 0.2.52 → 0.2.53-beta.10
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 +12 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -8,6 +8,18 @@ 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.10 (since v0.2.52)
|
|
12
|
+
|
|
13
|
+
### ✨ Improvements
|
|
14
|
+
- **A tool call that ended because the caller stopped is no longer reported as a gateway error** - A tool call whose caller stopped waiting was recorded with the same generic internal error as a tool server that had broken, so a session's activity could not tell the two apart. Such a call now carries its own reason, leaving the generic error for real failures.
|
|
15
|
+
- **An access request now takes its duration from the access policy** - An agent that asked for more access time than the policy allowed received an error instead of access, and nothing in the tool surface stated that limit. `create_access_request` no longer takes a duration: the access policy sets it, and on an account that requires an explicit duration the gateway asks for ten minutes, never more than the policy allows.
|
|
16
|
+
|
|
17
|
+
### 🛡️ Reliability
|
|
18
|
+
- **A failed call to a connected tool now records why it failed** - A call the gateway runs against a connected tool recorded only that it failed, so a caller that stopped waiting could not be told from a tool that broke. Each failure now carries its cause, which makes a recurring problem identifiable instead of hidden among every other failure of the same tool.
|
|
19
|
+
- **A refused tool call now records why it was refused** - A refused call recorded which tool failed but not the reason, so one cause could not be told from another when a problem recurred. Each refusal now carries its cause, which makes a repeating failure identifiable instead of indistinguishable from every other refusal of the same tool.
|
|
20
|
+
- **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.
|
|
21
|
+
- **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.
|
|
22
|
+
|
|
11
23
|
## Requirements
|
|
12
24
|
|
|
13
25
|
- Node.js 16 or later, for `npx`.
|