Get complete request and response details for a specific capture. Returns full HAR entry including: request headers, request body, response headers, response body (decoded text), status code, timing, server IP, and any WebSocket/SSE messages. Use the request ID from list_requests or search_requests.
AI agents call get_request to retrieve information from Proxypin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read operation that retrieves captured HTTP traffic data. However, severity is elevated to medium because the response body content could include sensitive data (API keys, credentials, PII, tokens) that an AI agent could expose or misuse if the captured traffic contains secrets. The tool itself performs no side effects, but the data it exposes carries risk depending on what was captured by ProxyPin.
From the tool's definition Tool returns 'complete request and response details' and 'full HAR entry including: request headers, request body, response headers, response body'. No modification, deletion, or execution described.
Attacks that exploit this kind of access
Get complete request and response details for a specific capture. Returns full HAR entry including: request headers, request body, response headers, response body (decoded text), status code, timing, server IP, and any WebSocket/SSE messages. Use the request ID from list_requests or search_requests. It is categorised as a Read tool in the Proxypin MCP Server, which means it retrieves data without modifying state.
Register the Proxypin MCP server in PolicyLayer and add a rule for get_request: 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 Proxypin. Nothing to install.
get_request 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_request 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_request. 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_request is provided by the Proxypin MCP server (k186/proxypin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →