// MCP TOOL REFERENCE

GLAZYR VIZ TOOLS

10 tools from the Glazyr Viz MCP Server, categorised by risk level.

READ TOOLS

browser_evaluate_js Evaluates arbitrary JavaScript in the GCP Big Iron browser context. 2/5 get_optic_nerve_status Returns a high-level dashboard of the agent's visual health, including FPS, latency, and Aquarium population metrics. get_remaining_credits Retrieve the current balance of cognitive frames available for this session. peek_vision_buffer Performs a low-latency 'peek' at the raw vision stream, returning resolution, sequence numbers, and optional base64 frame data. verify_payment Verifies a USDC transfer on the Base network to grant vision credits to the current session (1 USDC = 1,000,000 frames).

WRITE TOOLS

browser_click Legacy control: Dispatches a mouse click to the specified coordinates. 2/5 browser_set_fish_count Controls the hardware load by setting the number of active WebGL fish in the Aquarium simulation. 2/5 browser_type Legacy control: Types the specified text into the active browser element. 2/5

EXECUTE TOOLS

browser_navigate Dispatches a navigation command to the agent's browser, used to switch between benchmarks or sites. 3/5 run_dogfood_surge Executes the standardized dogfooding sequence: sets baseline, triggers a 30k fish surge, and returns status. 3/5

// FAQ

How many tools does the Glazyr Viz MCP server have? +

The Glazyr Viz MCP server exposes 10 tools across 3 categories: Read, Write, Execute.

How do I enforce policies on Glazyr Viz tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Glazyr Viz server.

What risk categories do Glazyr Viz tools fall into? +

Glazyr Viz tools are categorised as Read (5), Write (3), Execute (2). Each category has a recommended default policy.

Enforce policies on Glazyr Viz

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →