Look up a previous DPX settlement by settlement ID. Returns the full audit record: status, tx hash, amounts, fees, oracle conditions at time of settlement, ESG score, AI reasoning, and timestamp.
AI agents call get_settlement_status to retrieve information from Dpx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although the server facilitates financial settlement, this specific tool only queries and retrieves data about past settlements. It does not move money, create new settlements, or modify any state.
From the tool's definition Tool name is 'get_settlement_status' and description states it 'Look up a previous DPX settlement' and 'Returns the full audit record'.
Attacks that exploit this kind of access
Look up a previous DPX settlement by settlement ID. Returns the full audit record: status, tx hash, amounts, fees, oracle conditions at time of settlement, ESG score, AI reasoning, and timestamp. It is categorised as a Read tool in the Dpx MCP Server, which means it retrieves data without modifying state.
Register the Dpx MCP server in PolicyLayer and add a rule for get_settlement_status: 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_settlement_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_settlement_status 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_settlement_status. 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_settlement_status 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 →