bridge_state

L1 Bridge wiring + native escrow + delayed-message count (liveness/verification probe).

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

What bridge_state does on Z2 Zetrix

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

Why bridge_state needs a policy

This tool queries and retrieves state information about an L1 Bridge's wiring, escrow holdings, and delayed message counts for monitoring purposes. It is a read-only probe operation that does not create, modify, or delete data.

From the tool's definition L1 Bridge wiring + native escrow + delayed-message count (liveness/verification probe) - retrieves bridge state, escrow status, and message counts without modifying data

Questions about bridge_state

What does the bridge_state tool do? +

L1 Bridge wiring + native escrow + delayed-message count (liveness/verification probe). It is categorised as a Read tool in the Z2 Zetrix MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bridge_state? +

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

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

Can I rate-limit bridge_state? +

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

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

bridge_state 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

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