获取单个请求的完整详情，包括请求头、请求体、响应
AI agents call network_get_request_detail to retrieve information from Js Reverse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves network request details (headers, body, response) from a browser context without modifying or deleting data. It is a Read operation. Severity is high rather than low because: (1) the server's purpose is JS reverse engineering and crypto analysis for CTF/security contexts, (2) network request details can expose sensitive data like authentication tokens, API keys, encrypted credentials, and request…
From the tool's definition Tool name contains 'get' and description states '获取单个请求的完整详情' (retrieve complete details of a single request), including headers, body, and response. No modification or deletion occurs.
Attacks that exploit this kind of access
获取单个请求的完整详情，包括请求头、请求体、响应. 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 network_get_request_detail: 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.
network_get_request_detail 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 network_get_request_detail 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 network_get_request_detail. 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.
network_get_request_detail is provided by the Js Reverse MCP server (jenn619/js-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →