AI agents call browser_response_body to retrieve information from Wmux without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from previously captured network requests — a query operation with no ability to modify state, execute commands, delete data, or transfer funds. The most severe risk is accidental exposure of sensitive response bodies (headers, credentials, PII), but the act itself is read-only and reversible.
From the tool's definition Tool name is 'browser_response_body' and description states 'Retrieve the response body for a previously captured network request matching a URL pattern.' The verb 'Retrieve' and the read-only nature of accessing already-captured response data indicate pure…
Attacks that exploit this kind of access
Retrieve the response body for a previously captured network request matching a URL pattern. It is categorised as a Read tool in the Wmux MCP Server, which means it retrieves data without modifying state.
Register the Wmux MCP server in PolicyLayer and add a rule for browser_response_body: 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 Wmux. Nothing to install.
browser_response_body 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 browser_response_body 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 browser_response_body. 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.
browser_response_body is provided by the Wmux MCP server (openwong2kim/wmux). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
browser_response_body is one line of Wmux's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →