AI agents call http_history to retrieve information from Kali Security MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access http_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali Security MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for http_history:
{
"version": "1",
"default": "deny",
"tools": {
"http_history": {}
}
}http_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
查看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.
Deterministic rules across all 249 Kali Security MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
249 Kali Security MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.