browser_extract_text
Extract visible text content from an element. Useful for reading API keys, status messages, form values, etc.
This record as markdown: /tools/io-github-kivanccakmak-yaver/browser-extract-text.md
What browser_extract_text does on Yaver
AI agents call browser_extract_text to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
selector | string | — | CSS selector (default: body) |
session_id | string | Yes | Session ID |
Parameters from the server's own tool schema.
Why browser_extract_text is rated Low
The tool retrieves and queries text data from UI elements without side effects. While it can extract sensitive information like API keys, it remains a Read operation. Severity is medium rather than low because extracting API keys or credentials could enable privilege escalation or unauthorized access, but the tool itself only reads—it does not execute code, delete data, or move money.
From the tool's definition Tool explicitly performs extraction of visible text content from elements; description states it is 'useful for reading API keys, status messages, form values, etc.' These are all read operations with no modification of state.
Attacks that exploit this kind of access
The rule that runs browser_extract_text safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_extract_text, this is the rule to start with:
browser_extract_text is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every browser_extract_text call is checked against it from then on.
Questions about browser_extract_text
Extract visible text content from an element. Useful for reading API keys, status messages, form values, etc. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
browser_extract_text accepts 2 parameters: selector, session_id. Required: session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for browser_extract_text: 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 Yaver. Nothing to install.
browser_extract_text 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 browser_extract_text 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 browser_extract_text. 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.
browser_extract_text is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue