dcl_evaluate_trade
PRE-ACTION Trade Decision Verifier ($0.02). Screens trade-decision language for guaranteed-return claims, zero-risk/"can't lose" framing, and unqualified "buy/sell X now" directives — any match is NO_COMMIT. If no unsafe language is found, COMMIT additionally requires the word "risk" to appear an...
This record as markdown: /tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-trade.md
What dcl_evaluate_trade does on Dcl Trust Oracle
AI agents use dcl_evaluate_trade to commit financial operations through Dcl Trust Oracle, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_id | string | Yes | Identifier of the agent that produced the response. |
response | string | Yes | The trade decision or recommendation text to screen. |
Parameters from the server's own tool schema.
Why dcl_evaluate_trade is rated Critical
Tool screens financial trade decisions and produces trade receipts, directly gating financial actions.
From the tool's definition Trade Decision Verifier, trade-shape, guaranteed-return claims, buy/sell
Attacks that exploit this kind of access
The rule that runs dcl_evaluate_trade safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dcl Trust Oracle, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dcl_evaluate_trade, this is the rule to start with:
Any call to dcl_evaluate_trade is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Dcl Trust Oracle, apply this rule, and every dcl_evaluate_trade call is checked against it from then on.
Questions about dcl_evaluate_trade
PRE-ACTION Trade Decision Verifier ($0.02). Screens trade-decision language for guaranteed-return claims, zero-risk/"can't lose" framing, and unqualified "buy/sell X now" directives — any match is NO_COMMIT. If no unsafe language is found, COMMIT additionally requires the word "risk" to appear anywhere in the text as a minimum disclosure marker; its absence alone triggers NO_COMMIT with reason noting the missing disclosure. Produces an immutable trade_receipt (tx_hash/chain_hash/chain_depth) distinct from the top-level audit hash, for downstream systems that specifically need a trade-shaped receipt object. It is categorised as a Financial tool in the Dcl Trust Oracle MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
dcl_evaluate_trade accepts 2 parameters: agent_id, response. Required: agent_id, response. The full parameter table on this page comes from the server's own tool schema.
Register the Dcl Trust Oracle MCP server in PolicyLayer and add a rule for dcl_evaluate_trade: 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 Dcl Trust Oracle. Nothing to install.
dcl_evaluate_trade 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 dcl_evaluate_trade 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 dcl_evaluate_trade. 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.
dcl_evaluate_trade is provided by the Dcl Trust Oracle MCP server (https://mcp.fronesislabs.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dcl Trust Oracle, and thousands of servers like it.
Across the catalogue