AI agents call l1_query 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 |
|---|---|---|---|
method | string | Yes | |
params | object | — | |
contractAddress | string | Yes |
Parameters from the server's own tool schema.
This tool retrieves data from an L1 (Zetrix) contract without modifying state. The explicit 'read-only' designation and query semantics confirm it belongs to the Read category. Severity is low because it cannot cause financial transactions, data deletion, or code execution—only information retrieval.
From the tool's definition Tool description explicitly states 'read-only' and uses the term 'query' which indicates data retrieval with no side effects. The 'Escape hatch' qualifier suggests it is an exceptional access mechanism for querying L1 contract state.
Attacks that exploit this kind of access
Call an L1 (Zetrix) contract query interface (read-only). Escape hatch. It is categorised as a Read tool in the Z2 Zetrix MCP Server, which means it retrieves data without modifying state.
l1_query accepts 3 parameters: method, params, contractAddress. Required: method, contractAddress. 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 l1_query: 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.
l1_query 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 l1_query 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 l1_query. 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.
l1_query 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.
l1_query 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 →