Where an L2 withdrawal is + whether it can be claimed. Decodes the Withdrawal event, finds the covering assertion, checks confirmation, and (for native, or when the original ZTX3 rootToken is supplied) verifies the leaf against getSendRoot. leafKind 1/2/3.
AI agents call withdrawal_status 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 |
|---|---|---|---|
rootToken | string | — | original ZTX3 token — needed to verify a ZTP-20/721 leaf |
l2WithdrawTx | string | Yes |
Parameters from the server's own tool schema.
This tool retrieves and validates data about Layer 2 withdrawals to provide status information. It decodes events, checks confirmations, and verifies state—all read-only operations with no capacity to modify, delete, or execute code. The operations are queries against blockchain state and existing data structures.
From the tool's definition Tool name 'withdrawal_status' queries state: 'Decodes the Withdrawal event, finds the covering assertion, checks confirmation, and verifies the leaf'.
Attacks that exploit this kind of access
Where an L2 withdrawal is + whether it can be claimed. Decodes the Withdrawal event, finds the covering assertion, checks confirmation, and (for native, or when the original ZTX3 rootToken is supplied) verifies the leaf against getSendRoot. leafKind 1/2/3. It is categorised as a Read tool in the Z2 Zetrix MCP Server, which means it retrieves data without modifying state.
withdrawal_status accepts 2 parameters: rootToken, l2WithdrawTx. Required: l2WithdrawTx. 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 withdrawal_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 Z2 Zetrix. Nothing to install.
withdrawal_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 withdrawal_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 withdrawal_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.
withdrawal_status 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.
withdrawal_status 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 →