get_delx_wallet_status
Return wallet binding and custody mode for this agent. Requires agent_token. Free
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/get-delx-wallet-status.md
What get_delx_wallet_status does on Delx Protocol — Agent Recovery & Continuity
AI agents call get_delx_wallet_status to retrieve information from Delx Protocol — Agent Recovery & Continuity without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_id | string | Yes | Stable Delx agent identifier |
agent_token | string | Yes | Agent token returned by /api/v1/agents/register |
Parameters from the server's own tool schema.
Why get_delx_wallet_status is rated Low
This tool queries and retrieves wallet metadata (binding and custody mode) without modifying, deleting, or moving any funds. It requires authentication (agent_token) but performs no state changes. The blast radius of misuse is minimal—an unauthorized agent could learn wallet configuration details, which is a confidentiality concern but not a financial or destructive risk. Categorized as Read with low severity.
From the tool's definition Tool name and description indicate retrieval of wallet status information: 'Return wallet binding and custody mode for this agent.' The verb 'Return' and the informational nature of 'status' confirm a read operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_delx_wallet_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_delx_wallet_status, this is the rule to start with:
get_delx_wallet_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Protocol — Agent Recovery & Continuity, apply this rule, and every get_delx_wallet_status call is checked against it from then on.
Questions about get_delx_wallet_status
Return wallet binding and custody mode for this agent. Requires agent_token. Free. It is categorised as a Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.
get_delx_wallet_status accepts 2 parameters: agent_id, agent_token. Required: agent_id, agent_token. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for get_delx_wallet_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 Delx Protocol — Agent Recovery & Continuity. Nothing to install.
get_delx_wallet_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_delx_wallet_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_delx_wallet_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_delx_wallet_status is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.
Across the catalogue