New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_attack_session_details

获取攻击会话详情 - 查看指定会话的完整攻击历史。

SERVERKali Security MCP SOURCEseac-25/kali-security-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/seac-25-kali-security-mcp/get-attack-session-details.md

What get_attack_session_details does on Kali Security MCP

AI agents call get_attack_session_details 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 get_attack_session_details is rated Low

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.

Questions about get_attack_session_details

What does the get_attack_session_details tool do? +

获取攻击会话详情 - 查看指定会话的完整攻击历史。. It is categorised as a Read tool in the Kali Security MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_attack_session_details? +

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.

What risk level is get_attack_session_details? +

get_attack_session_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_attack_session_details? +

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.

How do I block get_attack_session_details completely? +

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.

What MCP server provides get_attack_session_details? +

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.

More on Kali Security, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Kali Security's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.