Returns a macro intelligence briefing from the DPX Stability Oracle — confidence scores, outlook, alerts, and forward signals across FX, climate, commodities, geopolitical risk, and yield. Each call is pay-per-use: 0.001 USDC on Base mainnet to 0x160e920012fb4BAe2E465c1eD8815c5FD51B5Ce0. Provide ...
AI agents use get_intelligence to commit financial operations through Dpx — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool triggers a financial transaction (USDC payment on Base mainnet) as a prerequisite for each call. Even though the primary function is data retrieval (macro intelligence briefing), the mechanism requires committing real on-chain financial value per use. Under the 'most severe applicable' rule, Financial supersedes Read.
From the tool's definition Each call is pay-per-use: 0.001 USDC on Base mainnet to 0x160e920012fb4BAe2E465c1eD8815c5FD51B5Ce0. Provide the payment txHash to unlock the response.
Attacks that exploit this kind of access
Returns a macro intelligence briefing from the DPX Stability Oracle — confidence scores, outlook, alerts, and forward signals across FX, climate, commodities, geopolitical risk, and yield. Each call is pay-per-use: 0.001 USDC on Base mainnet to 0x160e920012fb4BAe2E465c1eD8815c5FD51B5Ce0. Provide the payment txHash to unlock the response. If txHash is omitted or invalid, returns payment instructions (402) with the exact amount and address. Use focus and horizon to narrow the briefing. 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 get_intelligence: 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.
get_intelligence 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 get_intelligence 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 get_intelligence. 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.
get_intelligence 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.
get_intelligence is one line of Dpx's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →