List all saved history sessions from ProxyPin. Each session has a name, request count, file size, and creation time. Use get_history_requests to browse a session, or search_history to search across sessions.
AI agents call list_histories 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 metadata about saved HTTP traffic sessions without side effects. It is a pure query operation that lists existing sessions and their properties. No data is created, modified, deleted, or executed.
From the tool's definition Tool name 'list_histories' and description states it 'List all saved history sessions' with metadata like name, request count, file size, and creation time.
Attacks that exploit this kind of access
List all saved history sessions from ProxyPin. Each session has a name, request count, file size, and creation time. Use get_history_requests to browse a session, or search_history to search across sessions. 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_histories: 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_histories 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_histories 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_histories. 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_histories 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 →