Is a spend cap in the prompt a gate?
No. The agent can still name an over-cap item, or an unlimited approval, and proceed. A prompt line that says do not auto-send is not a control boundary.
Put a pre-execution gate between the agent’s proposal and checkout. Send the mandate including the cap, the proposed purchase, and the agent’s reasoning. Execute only when the gate returns ALLOW.
An agent can search, pick a listing, and move toward checkout without a separate check that the price matches the mandate. A spend cap in the prompt is not a gate. The agent can still name an over-cap item, or an unlimited approval, and proceed.
A pre-execution gate sits between the proposal and the action. You send three things: mandate (the user instruction, including the cap), proposed_action (title, price, URL), reasoning (why it picked that).
The gate returns a native verdict: ALLOW, BLOCK, or REVIEW, plus objections. On ThoughtProof DQL the axes are intent, scope, risk, consistency, and reversibility. execute is true only on ALLOW.
Call the gate before checkout, transfer, or unlimited approval. If the host ignores execute false, the gate did not fail. The integration did.
Install thoughtproof-mcp@0.3.2 and call verify_before_action / verify_decision with mode=dql. Keys at app.thoughtproof.ai/pricing. Same endpoint without a key: POST https://dql.thoughtproof.ai/dql/verify via x402 USDC on Base, $0.05 per live verify.
No. The agent can still name an over-cap item, or an unlimited approval, and proceed. A prompt line that says do not auto-send is not a control boundary.
Mandate (including the cap), proposed_action (title, price, URL), and reasoning. Native verdict ALLOW, BLOCK, or REVIEW, plus objections. execute is true only on ALLOW.
Mandate stay under $700; proposed action buy the $1,499 camera kit. The mismatch is on scope, and usually intent and consistency. A pass on a revision does not approve the first action.
The gate did not fail. The integration did. Call the gate before checkout, transfer, or unlimited approval.