diff --git a/README.md b/README.md
index 6f83fe56e..8c5af9015 100644
--- a/README.md
+++ b/README.md
@@ -713,6 +713,8 @@ Check the performance of https://developers.chrome.com
 
 > [!NOTE]
 > The <code>autoConnect</code> option requires the user to start Chrome. If the user has multiple active profiles, the MCP server will connect to the default profile (as determined by Chrome). The MCP server has access to all open windows for the selected profile.
+>
+> Network requests that occurred before the MCP server connected are not available via <code>list_network_requests</code> / <code>get_network_request</code>. If you need those, start the MCP server first or reload the page after it connects.
 
 The Chrome DevTools MCP server will try to connect to your running Chrome
 instance. It shows a dialog asking for user permission.
diff --git a/src/index.ts b/src/index.ts
index 362f2348a..0b754d676 100644
--- a/src/index.ts
+++ b/src/index.ts
@@ -199,6 +199,11 @@ export async function createMcpServer(
                 ? context.getPageById(params.pageId)
                 : context.getSelectedMcpPage();
             response.setPage(page);
+            if (page.getDialog() && tool.name !== 'handle_dialog') {
+              throw new Error(
+                'A browser dialog is open. Call handle_dialog to accept or dismiss it before continuing.',
+              );
+            }
             await tool.handler(
               {
                 params,