browser_describe

Read the current page: title, url, headings, interactive elements (with selectors), visible text, forms, modals, and errors. The primary observation channel — use before acting.

SERVERFlowDot MCP Server SOURCEflowdot-llc/mcp-server

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/flowdot-llc-mcp-server/browser-describe.md

WHAT IT DOES

What browser_describe does on FlowDot MCP Server

AI agents call browser_describe to retrieve information from FlowDot MCP Server 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_describe is rated Low

Even though browser_describe only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_describe safely

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

browser_describe Allowed

browser_describe 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_describe": {}
  }
}

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

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

FAQ

Questions about browser_describe

What does the browser_describe tool do? +

Read the current page: title, url, headings, interactive elements (with selectors), visible text, forms, modals, and errors. The primary observation channel — use before acting. It is categorised as a Read tool in the FlowDot MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_describe? +

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

What risk level is browser_describe? +

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

Can I rate-limit browser_describe? +

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

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

browser_describe is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FlowDot MCP Server, and thousands of servers like it.

This server

All 207 FlowDot MCP Server 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 →