AI agents call get_attack_session_details 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 retrieves historical information about attack sessions in a penetration testing context. While it is fundamentally a Read operation (no data modification), the severity is elevated to 'medium' because the retrieved attack session details could contain sensitive information about vulnerabilities, payloads, targets, or exploitation techniques that could be misused by an unauthorized agent.
From the tool's definition Tool name 'get_attack_session_details' and description 'view complete attack history of specified session' indicate data retrieval without modification.
Documented attack patterns abuse exactly the kind of access get_attack_session_details 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 get_attack_session_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_attack_session_details": {}
}
}get_attack_session_details 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.
获取攻击会话详情 - 查看指定会话的完整攻击历史。. 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 get_attack_session_details: 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.
get_attack_session_details 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_attack_session_details 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_attack_session_details. 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_attack_session_details 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.