This record as markdown: /tools/zebbern-zebbern-kali-mcp/payload-list.md
What payload_list does on Zebbern Kali MCP
AI agents call payload_list 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 payload_list is rated Low
The tool retrieves and queries a list of previously generated payloads from the Kali Linux penetration testing toolkit. While it only reads data without modifying or executing anything, the severity is elevated to 'medium' because the payloads themselves (when listed) represent weaponized artifacts for penetration testing.
From the tool's definition Tool name is 'payload_list' and description states 'List all generated payloads' — this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs payload_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zebbern Kali MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For payload_list, this is the rule to start with:
payload_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Zebbern Kali MCP, apply this rule, and every payload_list call is checked against it from then on.
Questions about payload_list
List all generated payloads. 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 payload_list: 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.
payload_list 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 payload_list 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 payload_list. 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.
payload_list 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.
This server
Across the catalogue