This record as markdown: /tools/seac-25-kali-security-mcp/http-history.md
What http_history does on Kali Security MCP
AI agents call http_history to retrieve information from Kali Security MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why http_history is rated Low
This tool queries and displays HTTP request history, which is a read-only operation that retrieves past data without creating, modifying, deleting, or executing any actions. The minimal blast radius if misused would be information disclosure of previously recorded HTTP interactions, but no system-altering consequences.
From the tool's definition Tool name 'http_history' and description '查看HTTP请求历史' (view HTTP request history) indicate retrieval of historical request data with no modification capability.
Attacks that exploit this kind of access
The rule that runs http_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kali Security MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For http_history, this is the rule to start with:
http_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Kali Security MCP, apply this rule, and every http_history call is checked against it from then on.
Questions about http_history
查看HTTP请求历史. It is categorised as a Read tool in the Kali Security MCP MCP Server, which means it retrieves data without modifying state.
Register the Kali Security MCP server in PolicyLayer and add a rule for http_history: 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 Kali Security MCP. Nothing to install.
http_history 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 http_history 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 http_history. 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.
http_history is provided by the Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kali Security, and thousands of servers like it.
This server
Across the catalogue