Generate a NEW L2 (EVM) account for the Z2 rollup — use its address as the l2Recipient of a deposit, and its private key as the l2Signer when withdrawing. Returns the address, private key, and mnemonic. Pure/local: NOTHING is sent on-chain and the key is NOT stored. SAVE THE PRIVATE KEY NOW — it ...
AI agents use create_l2_account to create or update resources in Z2 Zetrix — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Z2 Zetrix environment.
This tool creates new cryptographic key material and an associated L2 account. While the creation itself is local and reversible (accounts can be abandoned), the tool generates secrets (private key and mnemonic) that, once disclosed, grant control over assets. The primary action is account creation (Write category), not destruction or financial movement.
From the tool's definition Tool description states it 'Generate[s] a NEW L2 (EVM) account' and returns 'the address, private key, and mnemonic.' This creates a new account/keypair in the system.
Attacks that exploit this kind of access
Generate a NEW L2 (EVM) account for the Z2 rollup — use its address as the l2Recipient of a deposit, and its private key as the l2Signer when withdrawing. Returns the address, private key, and mnemonic. Pure/local: NOTHING is sent on-chain and the key is NOT stored. SAVE THE PRIVATE KEY NOW — it is shown once, cannot be recovered, and anyone holding it controls the account. (L2 accounts are plain EVM keypairs, unrelated to your L1 ZTX3 account.). It is categorised as a Write tool in the Z2 Zetrix MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Z2 Zetrix MCP server in PolicyLayer and add a rule for create_l2_account: 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.
create_l2_account is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_l2_account 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 create_l2_account. 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.
create_l2_account 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.
create_l2_account 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 →