com.browser-use/browser-use
com-browser-use-browser-use declares 7 capabilities across 7 tools, with 2 critical issues.
Issues
7 of 7 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
1 tool is classified as irreversible and declares no limit.
7 of 7 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
7 of 7 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
2 tools can modify data and declare no limit.
4 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
run_session | write |
inferred |
send_task | send |
inferred |
get_session | read |
inferred |
get_session_messages | read |
inferred |
stop_session | write |
assumed |
list_sessions | read |
inferred |
list_browser_profiles | read |
inferred |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-11 | 12 | tools/list answered by the PyPI package browser-use==0.13.5 (published to PyPI as browser-use, listed in the official MCP registry as com.browser-use/browser-use 0.13.5), run in an isolated container with no network access and no credentials |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.