Get detailed documentation, return values, examples, and caveats for any browser tool
AI agents call browser_docs to retrieve information from Browser MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a documentation/reference tool that queries and returns information about other browser tools. It performs read-only retrieval of static or pre-computed documentation content. There is no data modification, code execution with external effects, deletion, or financial impact. The blast radius of misuse is minimal since documentation retrieval cannot alter system state or compromise data integrity.
From the tool's definition Tool name 'browser_docs' and description 'Get detailed documentation, return values, examples, and caveats' indicates retrieval of informational content with no side effects on the browser state or data.
Attacks that exploit this kind of access
Get detailed documentation, return values, examples, and caveats for any browser tool. It is categorised as a Read tool in the Browser MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Browser MCP Server MCP server in PolicyLayer and add a rule for browser_docs: 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 Browser MCP Server. Nothing to install.
browser_docs 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_docs 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_docs. 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_docs is provided by the Browser MCP Server MCP server (madebytokens/browser-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →