AI agents invoke callback_start to trigger actions in Zebbern Kali MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool operates in a Kali Linux MCP server context alongside attack tools (ad_psexec, ad_wmiexec, ad_secretsdump, etc.), strongly suggesting it executes offensive operations. 'Callback' in penetration testing nomenclature typically means establishing a reverse shell or remote command execution channel—a classic Execute behavior.
From the tool's definition Tool named 'callback_start' with no description, operating within a Kali Linux penetration testing toolkit server that provides direct access to offensive security tools.
Documented attack patterns abuse exactly the kind of access callback_start 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 callback_start:
{
"version": "1",
"default": "deny",
"tools": {
"callback_start": {
"limits": [
{
"counter": "callback_start_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}callback_start stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
callback_start. It is categorised as a Execute tool in the Zebbern Kali MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Zebbern Kali MCP server in PolicyLayer and add a rule for callback_start: 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.
callback_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the callback_start 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 callback_start. 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.
callback_start 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.