crow_browser_capture_responses
Capture network responses (incl. JSON bodies) via raw CDP — the fastest way to find a site
This record as markdown: /tools/kh0pper-crow/crow-browser-capture-responses.md
What crow_browser_capture_responses does on Crow
AI agents call crow_browser_capture_responses to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crow_browser_capture_responses is rated Low
Capturing network responses is fundamentally a read operation: it retrieves data without modifying state. However, severity is medium rather than low because captured responses may contain sensitive data (API keys, authentication tokens, PII in JSON bodies), and an AI agent could misuse this to exfiltrate confidential information from sites it navigates to.
From the tool's definition Tool description states it 'Capture[s] network responses (incl. JSON bodies)' — a retrieval operation. The phrase 'via raw CDP' (Chrome DevTools Protocol) indicates passive monitoring of network traffic rather than modification or execution of external…
Attacks that exploit this kind of access
The rule that runs crow_browser_capture_responses safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_browser_capture_responses, this is the rule to start with:
crow_browser_capture_responses 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 Crow, apply this rule, and every crow_browser_capture_responses call is checked against it from then on.
Questions about crow_browser_capture_responses
Capture network responses (incl. JSON bodies) via raw CDP — the fastest way to find a site. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crow_browser_capture_responses: 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 Crow. Nothing to install.
crow_browser_capture_responses 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 crow_browser_capture_responses 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 crow_browser_capture_responses. 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.
crow_browser_capture_responses is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue