l2_call

Call an L2 (EVM) view. signature e.g. "balanceOf(address)"; outputs e.g. ["uint256"]. Escape hatch.

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

What l2_call does on Z2 Zetrix

AI agents call l2_call 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
to string Yes
args array
outputs array
signature string Yes

Parameters from the server's own tool schema.

Why l2_call needs a policy

The tool is described as calling an EVM 'view' function, which in Solidity/EVM terminology is a read-only call that does not modify state. However, it is described as an 'escape hatch' with arbitrary signature input, meaning it could potentially call non-view functions if misused. Confidence is slightly reduced due to the open-ended nature of the escape hatch, but the primary intent is read-only.

From the tool's definition Call an L2 (EVM) view. `signature` e.g. "balanceOf(address)"; `outputs` e.g. ["uint256"]. Escape hatch.

Questions about l2_call

What does the l2_call tool do? +

Call an L2 (EVM) view. signature e.g. "balanceOf(address)"; outputs e.g. ["uint256"]. Escape hatch. It is categorised as a Read tool in the Z2 Zetrix MCP Server, which means it retrieves data without modifying state.

What parameters does l2_call accept? +

l2_call accepts 4 parameters: to, args, outputs, signature. Required: to, signature. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on l2_call? +

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

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

Can I rate-limit l2_call? +

Yes. Add a rate_limit block to the l2_call 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 l2_call completely? +

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

l2_call 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

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