get_storage
Gets browser storage data including cookies, localStorage, and sessionStorage. Cookies are read via the Chrome DevTools Protocol (Network.getCookies), so httpOnly cookies (where auth/session tokens usually live) are included, along with rich attributes (domain, path, httpOnly, secure, sameSite, e...
This record as markdown: /tools/1600822305-js-reverse-mcp/get-storage.md
What get_storage does on Js Reverse
AI agents call get_storage to retrieve information from Js Reverse without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_storage is rated Low
This tool retrieves sensitive authentication tokens and session data (httpOnly cookies, localStorage, sessionStorage) from browser storage without modifying or deleting it.
From the tool's definition Tool description explicitly states it "Gets browser storage data" including cookies, localStorage, and sessionStorage. The verb "Gets" and "read" indicate data retrieval with no modification. No deletion, creation, or execution is described.
Attacks that exploit this kind of access
The rule that runs get_storage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Js Reverse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_storage, this is the rule to start with:
get_storage is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Js Reverse, apply this rule, and every get_storage call is checked against it from then on.
Questions about get_storage
Gets browser storage data including cookies, localStorage, and sessionStorage. Cookies are read via the Chrome DevTools Protocol (Network.getCookies), so httpOnly cookies (where auth/session tokens usually live) are included, along with rich attributes (domain, path, httpOnly, secure, sameSite, expires, etc.). localStorage and sessionStorage are read from the page context. It is categorised as a Read tool in the Js Reverse MCP Server, which means it retrieves data without modifying state.
Register the Js Reverse MCP server in PolicyLayer and add a rule for get_storage: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Js Reverse. Nothing to install.
get_storage is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_storage rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_storage. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_storage is provided by the Js Reverse MCP server (1600822305/js-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Js Reverse, and thousands of servers like it.
This server
Across the catalogue