# get_network_request

Gets a network request by an optional reqid, if omitted returns the currently selected request in the DevTools Network panel.

Agent View of the PolicyLayer registry record for `get_network_request`. HTML page: https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/get-network-request

## Facts

- Tool: `get_network_request`
- Server: Chrome DevTools MCP (`anirbandz/chrome_mcp_devtool`) — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool.md
- Homepage: https://github.com/Anirbandz/Chrome_MCP_DEVTOOL
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_network_request",
    "arguments": {}
  }
}
```

## Why get_network_request is rated Low

This tool retrieves and queries network request data from Chrome DevTools Network panel for inspection and debugging purposes. It does not execute code, modify state, delete data, or trigger external operations. The capability to inspect network requests is informational and poses minimal security risk in the context of an AI agent; the worst misuse would be information disclosure about intercepted network traffic.

From the tool's own definition: "Tool description states 'Gets a network request' — a retrieval operation with no modification or execution. The verb 'Gets' and the passive data retrieval nature confirm this is a Read operation that inspects network traffic without side effects."

## Use case

AI agents call get_network_request to retrieve information from Chrome DevTools MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Chrome DevTools MCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_network_request": {}
  }
}
```

## Other tools on Chrome DevTools MCP (25)

- `click` — Execute — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/click.md
- `drag` — Execute — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/drag.md
- `emulate` — Execute — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/emulate.md
- `evaluate_script` — Execute — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/evaluate-script.md
- `handle_dialog` — Execute — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/handle-dialog.md
- `hover` — Execute — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/hover.md
- `navigate_page` — Execute — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/navigate-page.md
- `new_page` — Execute — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/new-page.md
- `performance_start_trace` — Execute — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/performance-start-trace.md
- `performance_stop_trace` — Execute — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/performance-stop-trace.md
- `press_key` — Execute — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/press-key.md
- `resize_page` — Execute — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/resize-page.md
- `wait_for` — Execute — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/wait-for.md
- `get_console_message` — Read — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/get-console-message.md
- `list_console_messages` — Read — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/list-console-messages.md
- `list_network_requests` — Read — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/list-network-requests.md
- `list_pages` — Read — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/list-pages.md
- `performance_analyze_insight` — Read — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/performance-analyze-insight.md
- `take_screenshot` — Read — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/take-screenshot.md
- `take_snapshot` — Read — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/take-snapshot.md
- `close_page` — Write — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/close-page.md
- `fill` — Write — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/fill.md
- `fill_form` — Write — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/fill-form.md
- `select_page` — Write — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/select-page.md
- `upload_file` — Write — https://policylayer.com/tools/anirbandz-chrome-mcp-devtool/upload-file.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=anirbandz-chrome-mcp-devtool · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/anirbandz-chrome-mcp-devtool