Gets a network request by an optional reqid, if omitted returns the currently selected request in the DevTools Network panel.
AI agents call get_network_request to retrieve information from JS Reverse Strong MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reads network request data for inspection and analysis purposes. It does not modify, execute, delete, or trigger external operations. The sibling tools on this server (analyze_target, analyze_wasm_module, analyze_websocket_messages, etc.) are primarily analytical. While used in reverse engineering workflows, get_network_request itself is purely observational.
From the tool's definition Tool description states 'Gets a network request' — a retrieval operation with no side effects. It queries either a specified request ID or the currently selected request from the DevTools Network panel.
Documented attack patterns abuse exactly the kind of access get_network_request gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JS Reverse Strong MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_network_request:
{
"version": "1",
"default": "deny",
"tools": {
"get_network_request": {}
}
} get_network_request is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Gets a network request by an optional reqid, if omitted returns the currently selected request in the DevTools Network panel. It is categorised as a Read tool in the JS Reverse Strong MCP MCP Server, which means it retrieves data without modifying state.
Register the JS Reverse Strong MCP server in PolicyLayer and add a rule for get_network_request: 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 Strong MCP. Nothing to install.
get_network_request 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_network_request 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_network_request. 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_network_request is provided by the JS Reverse Strong MCP server (lwjjike/jsreverser-strong-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JS Reverse Strong MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
85 JS Reverse Strong MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.