Lists interactive elements and extracts content from the current page. Returns: str: A formatted string that lists all interactive elements (if any) along with the content.
AI agents call inspect_page to retrieve information from Mcp Browser Use without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
inspect_page performs read-only introspection of page state and content. It retrieves and presents information about the DOM and page elements without modifying, executing code, deleting data, or triggering external operations. This is a passive inspection capability typical of browser automation debugging tools.
From the tool's definition Tool description states it 'Lists interactive elements and extracts content from the current page' with a return value of formatted strings. The word 'extracts' and 'lists' are query/retrieval operations with no side effects.
Documented attack patterns abuse exactly the kind of access inspect_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Browser Use, and nothing reaches the server without passing your rules. This is the rule we recommend for inspect_page:
{
"version": "1",
"default": "deny",
"tools": {
"inspect_page": {}
}
}inspect_page is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists interactive elements and extracts content from the current page. Returns: str: A formatted string that lists all interactive elements (if any) along with the content. It is categorised as a Read tool in the Mcp Browser Use MCP Server, which means it retrieves data without modifying state.
Register the Mcp Browser Use MCP server in PolicyLayer and add a rule for inspect_page: 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 Mcp Browser Use. Nothing to install.
inspect_page 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 inspect_page 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 inspect_page. 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.
inspect_page is provided by the Mcp Browser Use MCP server (vinayak-mehta/mcp-browser-use). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Mcp Browser Use tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
19 Mcp Browser Use tools catalogued and risk-classified — across an index of 42,500+ MCP servers.