// SCAN REPORT

Z2 Zetrix

11 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 8 Jul 2026

1 can modify or destroy data

10 read-only

11 tools total

Community server · catalogue entry checked 08/07/2026 · full schemas captured for 9 of 11 tools

How to control Z2 Zetrix ↓

TOOL MAP

What Z2 Zetrix exposes to your agents

Read (10) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Z2 Zetrix costs in tokens

1,299 tokens of tool definitions, loaded on every request

0.6% of a 200k context window

189 heaviest tool: compute_leaf_hash

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Z2 Zetrix tools

Write · High create_l2_account This tool creates new cryptographic key material and an associated L2 account.

1 of Z2 Zetrix's 11 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Z2 Zetrix

PolicyLayer is an MCP gateway — it sits between your AI agents and Z2 Zetrix, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "create_l2_account": {
    "limits": [
      {
        "counter": "create_l2_account_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "bridge_state": {
    "limits": [
      {
        "counter": "bridge_state_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Z2 Zetrix — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON Z2 ZETRIX →

Instant setup, no code required.

FULL CATALOGUE

All 11 Z2 Zetrix tools

WRITE 1 tools

Write create_l2_account Generate a NEW L2 (EVM) account for the Z2 rollup — use its address as the l2Recipient of a deposit, and its p

READ 10 tools

Read bridge_state L1 Bridge wiring + native escrow + delayed-message count (liveness/verification probe). Read compute_leaf_hash Compute the Z2 exit-leaf hash (for pre-flight verification of a claim). leafKind: 1=WZETRIX(native), 2=TOKEN(Z Read derive_l2_address Derive the L2 EVM address (and 32-byte address slot) for an L1 ZTX3 token identifier = first 20 bytes of sha25 Read get_l1_transaction On-chain outcome of an L1 tx: { hash, status: CONFIRMED_OK|CONFIRMED_FAILED, errorCode, ledgerSeq } or null if Read get_l2_receipt L2 tx receipt: { status(1/0), blockNumber, logs } or null. Read l1_query Call an L1 (Zetrix) contract query interface (read-only). Escape hatch. Read l2_balance An account's L2 balance. asset: native → wZETRIX (resolved from the deployment, no address needed); ztp20/ztp7 Read l2_call Call an L2 (EVM) view. signature e.g. "balanceOf(address)"; outputs e.g. ["uint256"]. Escape hatch. Read token_info Resolve a mapped token: L1 metadata + derived L2 rootToken + L2 child address + bridge escrow. Read withdrawal_status Where an L2 withdrawal is + whether it can be claimed. Decodes the Withdrawal event, finds the covering assert

FAQ

Questions about Z2 Zetrix

How do I prevent bulk modifications through Z2 Zetrix? +

The Z2 Zetrix server has 1 write tools including create_l2_account. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Z2 Zetrix.

How many tools does the Z2 Zetrix MCP server expose? +

11 tools across 2 categories: Read, Write. 10 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Z2 Zetrix? +

Register the Z2 Zetrix MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Z2 Zetrix tool call.

Deterministic rules across all 11 Z2 Zetrix tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON Z2 ZETRIX →

Instant setup, no code required.

11 Z2 Zetrix tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Z2 Zetrix's registry record.

The record behind this page: 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 →