Extract focused page state by query. Returns headings, form fields, errors, tabs, and interactive counts scoped to the query intent.\n\nWhen to use: Checking focused aspects of page state (forms, errors, tabs) without loading the full DOM.\nWhen NOT to use: Use read_page for full DOM/AX tree, or ...
AI agents call inspect to retrieve information from OpenChrome without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only tool that queries and extracts information from a webpage without modifying, deleting, or executing code. While it controls a real Chrome browser, the inspect function itself only retrieves focused page state information. The capability to misuse is limited to information disclosure—the tool cannot perform actions, modify data, or trigger external operations.
From the tool's definition Tool explicitly returns page state information (headings, form fields, errors, tabs, interactive counts) without any modification or side effects.
Documented attack patterns abuse exactly the kind of access inspect gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenChrome, and nothing reaches the server without passing your rules. This is the rule we recommend for inspect:
{
"version": "1",
"default": "deny",
"tools": {
"inspect": {}
}
}inspect 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.
Extract focused page state by query. Returns headings, form fields, errors, tabs, and interactive counts scoped to the query intent.\n\nWhen to use: Checking focused aspects of page state (forms, errors, tabs) without loading the full DOM.\nWhen NOT to use: Use read_page for full DOM/AX tree, or find to locate a specific element. It is categorised as a Read tool in the OpenChrome MCP Server, which means it retrieves data without modifying state.
Register the OpenChrome MCP server in PolicyLayer and add a rule for inspect: 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 OpenChrome. Nothing to install.
inspect 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 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. 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 is provided by the OpenChrome MCP server (shaun0927/openchrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 106 OpenChrome tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
106 OpenChrome tools catalogued and risk-classified — across an index of 42,500+ MCP servers.