browser_get_request_detail

Get detailed information about a specific request, including curl command.

Server Playwright MCP Server leviathangk/playwrightmcpforcrawler
Category Read
Risk class Low
Parameters 00 required

What browser_get_request_detail does on Playwright MCP Server

AI agents call browser_get_request_detail to retrieve information from Playwright MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why browser_get_request_detail needs a policy

This tool queries and returns details about captured network requests—purely a read operation with no side effects. While the server as a whole supports browser automation (which can be misused), this specific tool is limited to retrieving request metadata and cannot modify state, execute code, delete data, or commit financial actions.

From the tool's definition Tool retrieves detailed information about a network request (including curl command representation), with no capability to modify, delete, or execute actions. The description uses 'Get', indicating a read-only retrieval operation.

Questions about browser_get_request_detail

What does the browser_get_request_detail tool do? +

Get detailed information about a specific request, including curl command. It is categorised as a Read tool in the Playwright MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_get_request_detail? +

Register the Playwright MCP Server MCP server in PolicyLayer and add a rule for browser_get_request_detail: 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.

What risk level is browser_get_request_detail? +

browser_get_request_detail is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browser_get_request_detail? +

Yes. Add a rate_limit block to the browser_get_request_detail 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.

How do I block browser_get_request_detail completely? +

Set action: deny in the PolicyLayer policy for browser_get_request_detail. 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.

What MCP server provides browser_get_request_detail? +

browser_get_request_detail is provided by the Playwright MCP Server MCP server (leviathangk/playwrightmcpforcrawler). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.