AI agents call get_l1_transaction 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 |
|---|---|---|---|
hash | string | Yes |
Parameters from the server's own tool schema.
This is a query/lookup operation that retrieves historical transaction status from a blockchain ledger. It has no side effects, does not modify state, does not execute code or trigger external operations, and does not delete or move funds. It is a pure read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_l1_transaction' and description specify retrieval of on-chain transaction outcome (hash, status, errorCode, ledgerSeq) with no modification or side effects. Returns data or null.
Attacks that exploit this kind of access
On-chain outcome of an L1 tx: { hash, status: CONFIRMED_OK|CONFIRMED_FAILED, errorCode, ledgerSeq } or null if not yet landed. It is categorised as a Read tool in the Z2 Zetrix MCP Server, which means it retrieves data without modifying state.
get_l1_transaction accepts 1 parameter: hash. Required: hash. 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 get_l1_transaction: 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.
get_l1_transaction 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 get_l1_transaction 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 get_l1_transaction. 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.
get_l1_transaction 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.
get_l1_transaction 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 →