Get live health status of local payment rails relevant to a settlement. Returns per-rail status (OPERATIONAL/DEGRADED/DOWN), latency, last incident, and a composite health score. Key rails: PIX (Brazil), SEPA (Europe), FedACH (US domestic), CHAPS (UK), UPI (India), PromptPay (Thailand). Call this...
AI agents call get_rail_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.
This tool queries real-time payment rail status across multiple international systems (PIX, SEPA, FedACH, CHAPS, UPI, PromptPay) and returns operational metrics. While it provides critical decision-support data for settlement operations, it performs no write, destructive, execute, or financial operations itself. It is pure information retrieval.
From the tool's definition Tool returns status information: 'Get live health status', 'Returns per-rail status (OPERATIONAL/DEGRADED/DOWN), latency, last incident, and a composite health score.' No modification, deletion, or financial transaction occurs.
Attacks that exploit this kind of access
Get live health status of local payment rails relevant to a settlement. Returns per-rail status (OPERATIONAL/DEGRADED/DOWN), latency, last incident, and a composite health score. Key rails: PIX (Brazil), SEPA (Europe), FedACH (US domestic), CHAPS (UK), UPI (India), PromptPay (Thailand). Call this before domestic or regionally-specific settlements to confirm the destination rail is healthy. A DEGRADED or DOWN rail should trigger a HOLD decision. 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_rail_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_rail_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_rail_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_rail_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_rail_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 →