derive_l2_address

Derive the L2 EVM address (and 32-byte address slot) for an L1 ZTX3 token identifier = first 20 bytes of sha256(utf8(ztx3)). Pure/local.

Server Z2 Zetrix z2-zetrix-mcp
Category Read
Risk class Low
Parameters 11 required

What derive_l2_address does on Z2 Zetrix

AI agents call derive_l2_address 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.

ParameterTypeRequiredDescription
ztx3 string Yes L1 ZTX3 token address

Parameters from the server's own tool schema.

Why derive_l2_address needs a policy

This tool only computes and returns a derived address based on deterministic cryptographic operations. It retrieves no data from external systems, creates no new state, executes no arbitrary code, and performs no destructive or financial operations. It is a pure mathematical function that fits the 'Read' category as a query/retrieval operation with no side effects.

From the tool's definition Tool is described as 'Pure/local' and performs cryptographic derivation of an L2 address from an L1 token identifier using SHA256 hashing. No state modification, external calls, or side effects occur.

Questions about derive_l2_address

What does the derive_l2_address tool do? +

Derive the L2 EVM address (and 32-byte address slot) for an L1 ZTX3 token identifier = first 20 bytes of sha256(utf8(ztx3)). Pure/local. It is categorised as a Read tool in the Z2 Zetrix MCP Server, which means it retrieves data without modifying state.

What parameters does derive_l2_address accept? +

derive_l2_address accepts 1 parameter: ztx3. Required: ztx3. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on derive_l2_address? +

Register the Z2 Zetrix MCP server in PolicyLayer and add a rule for derive_l2_address: 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.

What risk level is derive_l2_address? +

derive_l2_address is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit derive_l2_address? +

Yes. Add a rate_limit block to the derive_l2_address 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.

How do I block derive_l2_address completely? +

Set action: deny in the PolicyLayer policy for derive_l2_address. 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.

What MCP server provides derive_l2_address? +

derive_l2_address 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.

// THE FULL RECORD

derive_l2_address 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.