chrome-devtools-mcp icon indicating copy to clipboard operation
chrome-devtools-mcp copied to clipboard

Make reloading a page a separate tool

Open jonathanloske opened this issue 3 weeks ago • 2 comments

Is your feature request related to a problem? Please describe.

Background: IMHO, it is usually innocuous for an agent to reload a page but navigating to a new page is a totally different game. Currently, it is not easy to configure access rights for these separately as both these capabilities live under navigate_page. Therefore, it would be great if this could be a separate tool.

I am using Claude Code.

Describe the solution you'd like

To enhance security, it would be nice if reloading a page would be a separate tool, ie reload_page.

Describe alternatives you've considered

I've tried configuring just the reload functionality in .claude/settings.json but to no avail. This might be due to me not knowing how to configure sub-parts of tools.

Additional context

Configuring permissions in Claude Code:

  • https://code.claude.com/docs/en/iam#tool-specific-permission-rules
  • https://code.claude.com/docs/en/settings#permission-settings

jonathanloske avatar Dec 12 '25 08:12 jonathanloske

IIRC we consolidated tools into one after getting the feedback of having too many tools. From the implementation perspective a reload is a navigation and it might even redirect you to a different URL than expect. Is there a flexibility in Claude Code to configure permissions for specific params? We are planning to implement https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/239 which will apply navigation/network controls to all traffic irrespective of tool calls.

OrKoN avatar Dec 12 '25 10:12 OrKoN

I did not find the possibility of configuring permissions for specific params but it might just be that documentation is incomplete. #239 looks promising and would be very helpful indeed! It's not quite the same but would mostly suffice.

I definitely get that it's a back-and-forth to get the number of tools right. I also get that reload is indeed just a navigation to the same URL as currently loaded. Still it would be helpful, I think, to have it separate given that reloads will always only go back to a page the user had already been one which makes it a lot harder to trick the MCP into navigating to an arbitrary URL.

jonathanloske avatar Dec 12 '25 13:12 jonathanloske