browser_extract_attribute

Extract an HTML attribute value from an element (e.g., href, src, value, data-*).

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 33 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/browser-extract-attribute.md

WHAT IT DOES

What browser_extract_attribute does on Yaver

AI agents call browser_extract_attribute 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	Yes	CSS selector
`attribute`	string	Yes	Attribute name (e.g., href, value, data-id)
`session_id`	string	Yes	Session ID

Parameters from the server's own tool schema.

RISK

Why browser_extract_attribute is rated Low

This is a read-only operation that retrieves attribute values from DOM elements without side effects. It does not modify state, execute code, delete data, or commit financial transactions.

From the tool's definition Tool extracts HTML attribute values (href, src, value, data-*) from elements. The description explicitly states it 'extracts' data with no mention of modification, deletion, or execution capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_extract_attribute 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_attribute, this is the rule to start with:

browser_extract_attribute Allowed

browser_extract_attribute is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_extract_attribute": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every browser_extract_attribute call is checked against it from then on.

FAQ

Questions about browser_extract_attribute

What does the browser_extract_attribute tool do? +

Extract an HTML attribute value from an element (e.g., href, src, value, data-*). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does browser_extract_attribute accept? +

browser_extract_attribute accepts 3 parameters: selector, attribute, session_id. Required: selector, attribute, session_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on browser_extract_attribute? +

Register the Yaver MCP server in PolicyLayer and add a rule for browser_extract_attribute: 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.

What risk level is browser_extract_attribute? +

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

Can I rate-limit browser_extract_attribute? +

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

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

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

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

browser_extract_text on Percepta MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →