Get the native KXCO token balance of a wallet address on the Kxcoscan blockchain.
AI agents call wallet_balance to retrieve information from Kxcoscan AI Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves read-only blockchain data (wallet balance) without executing transactions, modifying state, or triggering any irreversible actions. It is a straightforward data query similar to a GET API call. No financial transaction occurs—it only reads existing balance information from the blockchain.
From the tool's definition Tool description states 'Get the native KXCO token balance of a wallet address' - a pure query operation with no modification, creation, or side effects.
Attacks that exploit this kind of access
Get the native KXCO token balance of a wallet address on the Kxcoscan blockchain. It is categorised as a Read tool in the Kxcoscan AI Tools MCP Server, which means it retrieves data without modifying state.
Register the Kxcoscan AI Tools MCP server in PolicyLayer and add a rule for wallet_balance: 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 Kxcoscan AI Tools. Nothing to install.
wallet_balance 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 wallet_balance 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 wallet_balance. 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.
wallet_balance is provided by the Kxcoscan AI Tools MCP server (keralpatel/kxcoscan-mcp-server). 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 →