An account's L2 balance. asset: native → wZETRIX (resolved from the deployment, no address needed); ztp20/ztp721 → supply the L1 ZTX3 token and the L2 child is resolved automatically. Use this to confirm a deposit minted on L2.
AI agents call l2_balance to retrieve information from Z2 Zetrix without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
asset | string | — | |
token | string | — | L1 ZTX3 token (required for ztp20/ztp721) |
holder | string | Yes | L2 EVM address (0x…) to check |
Parameters from the server's own tool schema.
This is a pure query operation that retrieves account balance data. It takes query parameters (account, asset type) and returns information without any capability to modify, transfer, or delete funds. The tool is used to 'confirm a deposit' (read operation). Even though it relates to financial assets, it performs only data retrieval, not financial movement, so it falls under Read rather than Financial.
From the tool's definition Tool retrieves 'An account's L2 balance' without modifying state. The description explicitly mentions querying balance information (native assets or ZTP20/ZTP721 tokens) with no mention of state changes, transfers, or side effects.
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
An account's L2 balance. asset: native → wZETRIX (resolved from the deployment, no address needed); ztp20/ztp721 → supply the L1 ZTX3 token and the L2 child is resolved automatically. Use this to confirm a deposit minted on L2. It is categorised as a Read tool in the Z2 Zetrix MCP Server, which means it retrieves data without modifying state.
l2_balance accepts 3 parameters: asset, token, holder. Required: holder. The full parameter table on this page comes from the server's own tool schema.
Register the Z2 Zetrix MCP server in PolicyLayer and add a rule for l2_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 Z2 Zetrix. Nothing to install.
l2_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 l2_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 l2_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.
l2_balance is provided by the Z2 Zetrix MCP server (z2-zetrix-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
l2_balance is one line of Z2 Zetrix's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →