browser_get_content

Get the text content, links, and forms from the current page.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

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/cowork-os/browser-get-content.md

WHAT IT DOES

What browser_get_content does on CoWork OS

AI agents call browser_get_content to retrieve information from CoWork OS 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_get_content is rated Low

This tool retrieves and queries information (text content, links, forms) from a web page without creating, modifying, deleting, or executing arbitrary operations. It is a passive read operation with minimal risk—the worst case is exposure of information already visible to the user. Classification as Read is appropriate.

From the tool's definition Tool name 'browser_get_content' and description 'Get the text content, links, and forms from the current page' indicate retrieval only with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_get_content safely

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

browser_get_content Allowed

browser_get_content 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_get_content": {}
  }
}

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

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

FAQ

Questions about browser_get_content

What does the browser_get_content tool do? +

Get the text content, links, and forms from the current page. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_get_content? +

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

What risk level is browser_get_content? +

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

Can I rate-limit browser_get_content? +

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

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

browser_get_content is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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