AI agents call token_info 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 |
|---|---|---|---|
rootToken | string | Yes | L1 ZTX3 token address |
Parameters from the server's own tool schema.
This tool retrieves and resolves information about mapped tokens across L1 and L2, returning metadata and derived addresses. It is a read-only query operation with no side effects, modifications, or financial impact. The low severity reflects minimal blast radius—an AI agent misusing this tool would only retrieve potentially sensitive token metadata, not cause irreversible damage or financial loss.
From the tool's definition Tool name 'token_info' and description 'Resolve a mapped token: L1 metadata + derived L2 rootToken + L2 child address + bridge escrow' indicate retrieval and resolution of token-related metadata and addresses.
Attacks that exploit this kind of access
Resolve a mapped token: L1 metadata + derived L2 rootToken + L2 child address + bridge escrow. It is categorised as a Read tool in the Z2 Zetrix MCP Server, which means it retrieves data without modifying state.
token_info accepts 1 parameter: rootToken. Required: rootToken. 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 token_info: 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.
token_info 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 token_info 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 token_info. 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.
token_info 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.
token_info 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 →