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

exploit_details

Get full details and source code for an exploit.

SERVERZebbern Kali MCP SOURCEzebbern/zebbern-kali-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/zebbern-zebbern-kali-mcp/exploit-details.md

What exploit_details does on Zebbern Kali MCP

AI agents call exploit_details to retrieve information from Zebbern Kali MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why exploit_details is rated Low

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.

Questions about exploit_details

What does the exploit_details tool do? +

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.

How do I enforce a policy on exploit_details? +

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.

What risk level is exploit_details? +

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

Can I rate-limit exploit_details? +

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.

How do I block exploit_details completely? +

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.

What MCP server provides exploit_details? +

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.

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

Across the catalogue

// 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 Zebbern Kali'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.