List recent captured HTTP(S) requests with summary info (method, URL, status code, response time). Returns newest first. Use this as the starting point to browse traffic, then call get_request with a specific ID to see full details including headers and response body.
AI agents call list_requests 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 tool retrieves and queries historical HTTP traffic metadata without side effects. It enables data discovery and inspection as a starting point for further analysis, but performs no write, delete, or execute operations. The blast radius of misuse is minimal—an AI agent could only view captured network traffic, which presents informational risk but no operational damage or data loss.
From the tool's definition Tool description explicitly states it 'List[s] recent captured HTTP(S) requests with summary info' and 'Returns newest first.' The verb is 'list' and the action is read-only browsing/inspection of already-captured traffic data.
Attacks that exploit this kind of access
List recent captured HTTP(S) requests with summary info (method, URL, status code, response time). Returns newest first. Use this as the starting point to browse traffic, then call get_request with a specific ID to see full details including headers and response body. 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 list_requests: 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.
list_requests 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 list_requests 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 list_requests. 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.
list_requests 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 →