deposit_outcome
Deposit ok/latency/quality after real use. Raises O in V(N,C,O,F); refills free kernel/loop events. Then optional WTP feedback.
This record as markdown: /tools/dev-dualregistry-registry/deposit-outcome.md
What deposit_outcome does on Dual Registry
AI agents use deposit_outcome to commit financial operations through Dual Registry, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
ok | boolean | — | |
body | string | — | |
from | string | — | |
kind | string | — | |
quality | number | — | 0-1 |
listing_b | string | — | |
latency_ms | number | — | |
listing_id | string | Yes |
Parameters from the server's own tool schema.
Why deposit_outcome is rated Critical
deposit_outcome moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs deposit_outcome safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dual Registry, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deposit_outcome, this is the rule to start with:
Any call to deposit_outcome is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Dual Registry, apply this rule, and every deposit_outcome call is checked against it from then on.
Questions about deposit_outcome
Deposit ok/latency/quality after real use. Raises O in V(N,C,O,F); refills free kernel/loop events. Then optional WTP feedback. It is categorised as a Financial tool in the Dual Registry MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
deposit_outcome accepts 8 parameters: ok, body, from, kind, quality, listing_b, latency_ms, listing_id. Required: listing_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dual Registry MCP server in PolicyLayer and add a rule for deposit_outcome: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Dual Registry. Nothing to install.
deposit_outcome is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deposit_outcome rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for deposit_outcome. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
deposit_outcome is provided by the Dual Registry MCP server (https://www.dualregistry.dev/api/protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dual Registry, and thousands of servers like it.
Across the catalogue