Get full details and source code for an exploit.
AI agents call exploit_details to retrieve information from Zebbern Kali MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves exploit information and code but does not execute exploits, modify systems, or cause destructive actions. It is a Read operation. Severity is high because in the context of a Kali Linux penetration testing toolkit, providing detailed exploit code and methodology to an AI agent could enable sophisticated attacks if the agent is compromised or misdirected.
From the tool's definition Tool name is 'exploit_details' and description states 'Get full details and source code for an exploit' — the verb 'Get' and action of retrieving information (details, source code) with no modification or execution indicated.
Documented attack patterns abuse exactly the kind of access exploit_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zebbern Kali MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for exploit_details:
{
"version": "1",
"default": "deny",
"tools": {
"exploit_details": {}
}
}exploit_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.
Get full details and source code for an exploit. It is categorised as a Read tool in the Zebbern Kali MCP MCP Server, which means it retrieves data without modifying state.
Register the Zebbern Kali MCP server in PolicyLayer and add a rule for exploit_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 Zebbern Kali MCP. Nothing to install.
exploit_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 exploit_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 exploit_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.
exploit_details is provided by the Zebbern Kali MCP server (zebbern/zebbern-kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 128 Zebbern Kali MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
128 Zebbern Kali MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.