Execute a DPX settlement — cross-border or domestic (intra-country). The Settlement Agent checks oracle conditions and local rail health, reasons about whether conditions are right, and executes on-chain (or returns sandbox result if sandbox=true). Same-currency settlements (e.g. USD→USD) skip th...
AI agents use settle to commit financial operations through Dpx — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves real funds via on-chain transactions when sandbox=false. It commits financial obligations through cross-border or domestic settlement using USDC/EURC stablecoins. The ability to execute live on-chain payments with real money makes this Financial category, and the critical severity reflects the potential blast radius of an AI agent misusing it to move large sums irreversibly across borders.
From the tool's definition Execute a DPX settlement — cross-border or domestic... executes on-chain... USDC/EURC settlement on Base at 1.385% all-in... Set sandbox=false only when ready for live execution
Attacks that exploit this kind of access
Execute a DPX settlement — cross-border or domestic (intra-country). The Settlement Agent checks oracle conditions and local rail health, reasons about whether conditions are right, and executes on-chain (or returns sandbox result if sandbox=true). Same-currency settlements (e.g. USD→USD) skip the FX fee automatically. Returns settlement ID, status (executed/held/sandbox/failed), tx hash, net amount, fees, oracle status, and AI reasoning. IMPORTANT: By default runs in sandbox mode (no real funds moved). Set sandbox=false only when ready for live execution. It is categorised as a Financial tool in the Dpx MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Dpx MCP server in PolicyLayer and add a rule for settle: 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 Dpx. Nothing to install.
settle 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 settle 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 settle. 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.
settle is provided by the Dpx MCP server (untitledfinancial/dpx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →