get_cookies
Reads cookies via the CDP Network domain, including httpOnly cookies
This record as markdown: /tools/1600822305-js-reverse-mcp/get-cookies.md
What get_cookies does on Js Reverse
AI agents call get_cookies 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_cookies is rated Low
This tool retrieves sensitive session and authentication data (cookies, including httpOnly variants) from a browser without modifying or deleting them. While categorically a Read operation, the severity is high because cookies often contain authentication tokens, session IDs, and personal data that could be misused for account compromise, session hijacking, or privacy violations if an AI agent extracts them without…
From the tool's definition Tool name 'get_cookies' and description 'Reads cookies via the CDP Network domain, including httpOnly cookies' explicitly indicates data retrieval with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs get_cookies 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_cookies, this is the rule to start with:
get_cookies 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_cookies call is checked against it from then on.
Questions about get_cookies
Reads cookies via the CDP Network domain, including httpOnly cookies. 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_cookies: 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_cookies 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_cookies 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_cookies. 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_cookies 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