New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_delx_wallet_status

Return wallet binding and custody mode for this agent. Requires agent_token. Free

SERVERDelx MCP Server SOURCEdelx-mcp-server
Low RISK CLASS
Category Read
Parameters 22 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/get-delx-wallet-status.md

What get_delx_wallet_status does on Delx MCP Server

AI agents call get_delx_wallet_status to retrieve information from Delx MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
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 retrieves wallet status information for an agent without modifying state, executing commands, or triggering financial transactions. It is a straightforward query operation. The 'Free' designation confirms no financial commitments are made.

From the tool's definition Tool name contains 'get_' prefix and description states 'Return wallet binding and custody mode' - a retrieval operation with no modification or side effects. Marked 'Free' indicating read-only access.

Questions about get_delx_wallet_status

What does the get_delx_wallet_status tool do? +

Return wallet binding and custody mode for this agent. Requires agent_token. Free. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.

What parameters does get_delx_wallet_status accept? +

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.

How do I enforce a policy on get_delx_wallet_status? +

Register the Delx MCP Server 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 MCP Server. Nothing to install.

What risk level is get_delx_wallet_status? +

get_delx_wallet_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_delx_wallet_status? +

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.

How do I block get_delx_wallet_status completely? +

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.

What MCP server provides get_delx_wallet_status? +

get_delx_wallet_status is provided by the Delx MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Delx MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Delx MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.