end_attack_session
结束当前攻击会话 - 完成日志记录并保存会话数据。
This record as markdown: /tools/seac-25-kali-security-mcp/end-attack-session.md
What end_attack_session does on Kali Security MCP
AI agents use end_attack_session to create or update resources in Kali Security MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kali Security MCP environment.
Why end_attack_session is rated Medium
This tool ends an attack session by finalizing logs and saving session data. The primary action is writing/saving data (session records, logs) rather than executing attacks or destroying data. It is a cleanup/bookkeeping operation.
From the tool's definition 结束当前攻击会话 - 完成日志记录并保存会话数据 (End current attack session - complete logging and save session data)
Attacks that exploit this kind of access
The rule that runs end_attack_session 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 end_attack_session, this is the rule to start with:
end_attack_session stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 end_attack_session call is checked against it from then on.
Questions about end_attack_session
结束当前攻击会话 - 完成日志记录并保存会话数据。. It is categorised as a Write tool in the Kali Security MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kali Security MCP server in PolicyLayer and add a rule for end_attack_session: 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.
end_attack_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the end_attack_session 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 end_attack_session. 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.
end_attack_session 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