@metamynd/agentsafe-mcp-guard 0.2.1 → 0.3.1

package/README.md

@@ -67,6 +67,11 @@ const bookFlight = guard.guardIncomingTool('flight-purchase', rawBookFlight);
 4. evaluates Standards → SOPs → mandate with `policy-core` — signed fields applied last, so a
    forged `itinerary` key can't shadow the signed amount/merchant (§6.4.2).
 
+`policy-core`'s `amount-unknown` atom (0.3.0) is a deny-by-default check for any value-moving
+tool call whose amount the guard can't determine — a signed-transaction or nested x402 payload
+can carry its value somewhere a naive spend cap never looks, and this blocks that case instead
+of letting it slip past the cap untested.
+
 ### Replay and cumulative spend (`requireAuthorization`)
 
 Re-evaluating policy per request (above) proves the request is well-formed and in-policy — it

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metamynd/agentsafe-mcp-guard",
-  "version": "0.2.1",
+  "version": "0.3.1",
   "description": "Zero-dependency trustless governance for the SERVICE side. An MCP server or API re-verifies a calling agent's signed request against the agent's own published policy \u00e2\u20ac\u201d so an agent that ignores its own guard still cannot make your service act.",
   "type": "module",
   "main": "./agentsafe-mcp-guard.mjs",

package/policy-core.mjs

@@ -11,6 +11,14 @@ var ATOM_REGISTRY = {
     return have !== void 0 && need !== void 0 && have >= need;
   },
   "amount-over": (c, cfg) => typeof c.amount === "number" && c.amount > Number(cfg?.limit ?? 0),
+  // Deny-by-default primitive for value-moving actions. Fires on ABSENCE (like the
+  // evidence atoms below, and unlike `amount-over`): true when the context carries no
+  // usable amount — the gate cannot tell how much value the call would move, so a
+  // spend cap authored next to it would silently never fire. Author it with BLOCK as
+  // the FIRST rule of a spend policy; the cap that follows then only ever judges a
+  // known number. Opt-in: only a rule that keys it runs it, so actions that carry no
+  // amount by nature are unaffected.
+  "amount-unknown": (c) => !(typeof c.amount === "number" && Number.isFinite(c.amount)),
   // Total budget: cumulativeSpend is a SERVER-derived, signed-last context field (never
   // shadowable by the agent's itinerary), so this compares already-spent + this amount.
   "cumulative-over": (c, cfg) => Number(c.cumulativeSpend ?? 0) + Number(c.amount ?? 0) > Number(cfg?.limit ?? 0),
@@ -72,6 +80,13 @@ var ATOM_SPECS = [
     config: [{ key: "limit", type: "number", required: true, description: "Maximum allowed amount for one transaction" }],
     requiredContext: ["amount"]
   },
+  {
+    predicate: "amount-unknown",
+    label: "Amount not determinable",
+    description: "Fires when the action carries no usable amount \u2014 the gate cannot tell how much value it would move. A deny-by-default control for value-moving actions: author it with BLOCK ahead of a spend cap, otherwise an action whose amount is missing or unparseable passes the cap untested. Fires on ABSENCE, so only attach it to actions that must always carry an amount.",
+    config: [],
+    requiredContext: ["amount"]
+  },
   {
     predicate: "cumulative-over",
     label: "Total budget over limit",