AI agents call get_history_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 is a read-only tool that retrieves metadata about previously captured HTTP requests. It has no side effects, cannot modify or delete data, and does not execute code or external operations. The summary-only output and explicit reference to using get_history_detail for full inspection confirms this is a data retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool returns summary info only (method, URL, status, time) from saved history sessions. No modification, deletion, or execution capability—purely retrieves and queries stored HTTP request data.
Attacks that exploit this kind of access
Get requests from a saved history session. Returns summary info only (method, URL, status, time). Use get_history_detail with a specific ID for full headers and 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 get_history_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.
get_history_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 get_history_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 get_history_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.
get_history_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 →