// MCP TOOL REFERENCE

YETIBROWSER MCP TOOLS

17 tools from the YetiBrowser MCP MCP Server, categorised by risk level.

// ALL 17 YETIBROWSER MCP TOOLS

READ 6 tools

Read browser_connection_info Show the MCP bridge WebSocket port, connection state, and extension info Read browser_get_console_logs Get the console logs from the browser Read browser_screenshot Take a screenshot of the current page Read browser_snapshot Capture accessibility snapshot of the current page. Use this for getting references to elements to interact... Read browser_snapshot_diff Compare the most recent snapshot with the previous one to highlight DOM changes Read browser_page_state Extract form data, storage values, and cookies from the active page

EXECUTE 11 tools

Execute browser_evaluate Run custom JavaScript inside the page context and return the JSON-serializable result. Execute browser_wait Wait for a specified time in seconds Execute browser_wait_for Wait until a selector appears (optionally visible) before continuing. Returns a fresh snapshot after the el... Execute browser_click Perform click on a web page Execute browser_drag Drag an element (like cards in a kanban board) onto a target element. Useful for sortable UIs. Execute browser_fill_form Fill multiple form fields in a single call. Supports inputs, textareas, selects, checkboxes, and radios. Execute browser_handle_dialog Accept or dismiss the currently open alert/confirm/prompt dialog in the active tab. Execute browser_hover Hover over element on page Execute browser_press_key Press a key on the keyboard Execute browser_select_option Select an option in a dropdown Execute browser_type Type text into editable element

// FAQ

How many tools does the YetiBrowser MCP MCP server have? +

The YetiBrowser MCP MCP server exposes 17 tools across 2 categories: Read, Execute.

How do I enforce policies on YetiBrowser MCP tools? +

Route the YetiBrowser MCP server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do YetiBrowser MCP tools fall into? +

YetiBrowser MCP tools are categorised as Read (6), Execute (11). Each category has a recommended default policy.

Enforce policy on every YetiBrowser MCP tool call.

Start from YetiBrowser MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.