Repository navigation
Report non-scriptable pages the same way (AGE-259) - #256
Merged
Merged
Conversation
chrome://, DevTools, view-source, the Chrome Web Store, extension pages, and the PDF viewer now return access "metadata-only" and the wording "metadata only, can't read or act", so agents stop treating those pages as scriptable. An http(s) PDF can still load and is reported after. Co-authored-by: werbel.ted <werbel.ted@gmail.com>
cursor
Bot
force-pushed
the
cursor/age-259-restricted-page-reporting-555d
branch
from
October 27, 2026 04:34
f94daae to
a46d3e2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Agents that land on a page the extension cannot script now get one shared result instead of a generic "only http(s)" or an empty log.
The fields, for navigation errors, page info, and each tab in
listBrowserTabs:access:"metadata-only"message:"metadata only, can't read or act"scriptable:falsekind:chrome,devtools,view-source,web-store,pdf,extension, orbrowserdetail: one sentence naming the pageAGE-584's tab list and background navigate can import
restrictedPage/restrictedPageFieldsfrombrowser-tools-mcp/src/restricted-page.tsand keep this wording.Covered pages:
chrome://(andchrome-error://,chrome-untrusted://),devtools://,view-source:, the Chrome Web Store (chromewebstore.google.comandchrome.google.com/webstore), extension pages, the built-in PDF viewer (Chromium idmhjfbmdgcfjbbpaeojofohoefgiehjaiand*.pdf), plusedge://,brave://, and similar browser pages.about:blankstays scriptable.Behavior:
structuredContentagainst the success schema, so the object is in the text). The local API returns HTTP 422RESTRICTED_PAGEwith the same fields.navigated: true) and the viewer cannot be scripted.getPageInfoandlistBrowserTabsstay successful and include the fields, because listing the page is the metadata that is allowed.No version bump, no npm publish, no Vitest change.
Tests
npm test(unit + integration): 36 files, 573 tests passed.browser-tools-mcp/test/unit/restricted-page.test.ts— classification and the shared error objectbrowser-tools-mcp/test/unit/capability-gates.test.ts— leave achrome://tab; still refuse acting on itbrowser-tools-mcp/test/integration/restricted-page.test.ts— connector, local API, HTTP client, MCP tools, and the CLI invoke pathconnector-flowandconnector-security