browser_read

Read text/html/value/url/title from the page.

SERVERHercules MCP SOURCE0xmihirk/hercules-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xmihirk-hercules-mcp/browser-read.md

WHAT IT DOES

What browser_read does on Hercules MCP

AI agents call browser_read to retrieve information from Hercules MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why browser_read is rated Low

This tool retrieves information from a web page without modifying, executing, or deleting anything. It is a straightforward read operation. While this server exposes penetration testing capabilities (including bruteforce tools), this specific tool is constrained to reading page content.

From the tool's definition Tool name includes 'read' and description explicitly states 'Read text/html/value/url/title from the page' — a passive data retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_read safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hercules MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_read, this is the rule to start with:

browser_read Allowed

browser_read 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_read": {}
  }
}

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

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

FAQ

Questions about browser_read

What does the browser_read tool do? +

Read text/html/value/url/title from the page. It is categorised as a Read tool in the Hercules MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_read? +

Register the Hercules MCP server in PolicyLayer and add a rule for browser_read: 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 Hercules MCP. Nothing to install.

What risk level is browser_read? +

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

Can I rate-limit browser_read? +

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

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

browser_read is provided by the Hercules MCP server (0xmihirk/hercules-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hercules, and thousands of servers like it.

This server

All 45 Hercules tools →

Across the catalogue

claude_read_file on Claude Bridge →browser_extract_text on Percepta MCP Server → The MCP Attack Database →

Guides

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