inspect_requests
Deep-inspect FULL captured request/response detail for ONE host — method, URL, request + response HEADERS, and request + response BODIES (size-capped). The tool for reverse-engineering how a real app/API works from its actual captured traffic (auth flows, required headers, payload shapes) and for...
This record as markdown: /tools/dev-busymate-busymate-devtools/inspect-requests.md
What inspect_requests does on Busymate DevTools
AI agents call inspect_requests to retrieve information from Busymate DevTools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
host | string | Yes | FULL hostname (must contain a dot), e.g. 'identity.doordash.com'. Bare brand words are rejected. |
after | string | — | Optional — only requests with ts >= this ISO date/datetime, e.g. '2025-05-20'. |
limit | number | — | Max requests (default 8, capped at 15). |
before | string | — | Optional — only requests with ts < this ISO date/datetime ('before/older than <date>'). |
method | string | — | Optional HTTP method filter, e.g. POST. |
status | number | — | Optional exact response status filter, e.g. 200. |
deviceName | string | — | |
device_uuid | string | — | |
path_contains | string | — | Optional — only requests whose path contains this substring (e.g. 'login', 'token', 'auth'). |
Parameters from the server's own tool schema.
Why inspect_requests is rated Low
This tool reads and inspects existing captured network traffic without modifying, deleting, or executing code. It is a diagnostic/inspection tool that retrieves detailed request/response information.
From the tool's definition Tool performs 'Deep-inspect FULL captured request/response detail' and is 'for reverse-engineering how a real app/API works from its actual captured traffic' — retrieves and queries previously captured HTTPS traffic data with no modification or execution…
Risk signalsAccepts URL/endpoint input (host)
Attacks that exploit this kind of access
The rule that runs inspect_requests safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Busymate DevTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For inspect_requests, this is the rule to start with:
inspect_requests 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 Busymate DevTools, apply this rule, and every inspect_requests call is checked against it from then on.
Questions about inspect_requests
Deep-inspect FULL captured request/response detail for ONE host — method, URL, request + response HEADERS, and request + response BODIES (size-capped). The tool for reverse-engineering how a real app/API works from its actual captured traffic (auth flows, required headers, payload shapes) and for building repro (curl/fetch). host MUST be a full hostname containing a dot (e.g. 'identity.doordash.com') — a bare brand word is rejected (an exact-host index scan is fast; a substring scan times out). Scoped to a device (device_uuid/deviceName) it scans that device's full history; WITHOUT a device (fleet-wide) it defaults to the last 7 days — pass after/before (up to 31 days back) to widen. Optionally narrow by path substring, method, or status. Newest first. Treat any tokens / cookies / credentials in headers + bodies as SECRETS. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.
inspect_requests accepts 9 parameters: host, after, limit, before, method, status, deviceName, device_uuid, path_contains. Required: host. The full parameter table on this page comes from the server's own tool schema.
Register the Busymate DevTools MCP server in PolicyLayer and add a rule for inspect_requests: 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 Busymate DevTools. Nothing to install.
inspect_requests 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 inspect_requests 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 inspect_requests. 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.
inspect_requests is provided by the Busymate DevTools MCP server (https://mcp.busymate.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Busymate DevTools, and thousands of servers like it.
This server
Across the catalogue