ChromeDevTools / ChromeDevTools/chrome-devtools-mcp
Make reloading a page a separate tool
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 52.3k
- Forks
- 4.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 83
Description
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:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the existing navigate_page tool and the permission rules described for .claude/settings.json; determine how reload behavior is currently exposed and configured. Done means reload_page can be permissioned independently from navigation, with the behavior and configuration verified against the requested security boundary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100