inspect_console_object
Inspect a JavaScript object or expression in detail. Args: expression: JavaScript expression to inspect Returns: Detailed object inspection results
This record as markdown: /tools/benjaminr-chrome-devtools-mcp/inspect-console-object.md
What inspect_console_object does on Chrome Devtools
AI agents invoke inspect_console_object to trigger actions in Chrome Devtools. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why inspect_console_object is rated High
Although framed as 'inspect', the tool takes a JavaScript expression as input and evaluates it in the browser, which constitutes code execution. An AI agent could pass arbitrary JS expressions that have side effects beyond mere inspection. This is consistent with sibling tools like execute_javascript and evaluate_in_all_frames, confirming the server executes JS in browser contexts.
From the tool's definition 'Inspect a JavaScript object or expression in detail' and 'JavaScript expression to inspect' — the tool evaluates an arbitrary JavaScript expression in the browser context
Attacks that exploit this kind of access
The rule that runs inspect_console_object safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For inspect_console_object, this is the rule to start with:
inspect_console_object stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every inspect_console_object call is checked against it from then on.
Questions about inspect_console_object
Inspect a JavaScript object or expression in detail. Args: expression: JavaScript expression to inspect Returns: Detailed object inspection results. It is categorised as a Execute tool in the Chrome Devtools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Chrome Devtools MCP server in PolicyLayer and add a rule for inspect_console_object: 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 Chrome Devtools. Nothing to install.
inspect_console_object is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the inspect_console_object 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_console_object. 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_console_object is provided by the Chrome Devtools MCP server (benjaminr/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chrome Devtools, and thousands of servers like it.
Across the catalogue