get_response_body
A read tool on the Playwright MCP server.
This record as markdown: /tools/alexrwilliam-playwright-mcp-server/get-response-body.md
What get_response_body does on Playwright MCP Server
AI agents call get_response_body to retrieve information from Playwright MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_response_body is rated Low
This tool retrieves response body content from web requests—a read operation with no side effects on the target system or the browser state. While it could theoretically exfiltrate sensitive data if the target page contains such content, the tool itself performs only data retrieval. Severity is low because misuse would be limited to information disclosure rather than modification, deletion, or code execution.
From the tool's definition Tool name 'get_response_body' indicates retrieval of HTTP response content from a webpage interaction. The sibling tools include browser automation actions (click, evaluate, check_checkbox) and data clearing operations, positioning this tool as a data…
Attacks that exploit this kind of access
The rule that runs get_response_body safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Playwright MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_response_body, this is the rule to start with:
get_response_body 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 Playwright MCP Server, apply this rule, and every get_response_body call is checked against it from then on.
Questions about get_response_body
get_response_body is a read tool on the Playwright MCP Server MCP server. It is categorised as a Read tool in the Playwright MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Playwright MCP Server MCP server in PolicyLayer and add a rule for get_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 Playwright MCP Server. Nothing to install.
get_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 get_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 get_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.
get_response_body is provided by the Playwright MCP Server MCP server (alexrwilliam/playwright-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Playwright MCP Server, and thousands of servers like it.
This server
Across the catalogue