Check if trade execution is enabled and get wallet balance.
AI agents call get_wallet_status to retrieve information from TradeX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves wallet information and status checks—no creation, modification, deletion, or execution of transactions. Even though it operates in a financial context (cryptocurrency/trading platform), it performs only read operations on existing data. The severity is low because misuse would only expose information, not cause financial loss or unauthorized transactions.
From the tool's definition Tool name 'get_wallet_status' and description 'Check if trade execution is enabled and get wallet balance' indicate pure data retrieval with no side effects. It queries state without modifying it.
Attacks that exploit this kind of access
Check if trade execution is enabled and get wallet balance. It is categorised as a Read tool in the TradeX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TradeX MCP Server MCP server in PolicyLayer and add a rule for get_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 TradeX MCP Server. Nothing to install.
get_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_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_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_wallet_status is provided by the TradeX MCP Server MCP server (tradexcards/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 →