callback_clear

A destructive tool on the Zebbern Kali MCP server.

SERVERZebbern Kali MCP SOURCEzebbern/zebbern-kali-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/zebbern-zebbern-kali-mcp/callback-clear.md

WHAT IT DOES

What callback_clear does on Zebbern Kali MCP

AI agents call callback_clear to permanently remove resources in Zebbern Kali MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why callback_clear is rated Critical

The description is empty, which lowers confidence. However, the name 'callback_clear' on a penetration testing platform suggests clearing callback/listener configurations, reverse shell listeners, or C2 callback records — an action that would be irreversible and destructive in nature.

From the tool's definition Tool name 'callback_clear' on a Kali Linux penetration testing MCP server with sibling tools including secretsdump, psexec, wmiexec, and various AD attack tools.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs callback_clear 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 callback_clear, this is the rule to start with:

callback_clear Hidden

callback_clear is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "callback_clear"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Zebbern Kali MCP, apply this rule, and every callback_clear call is checked against it from then on.

FAQ

Questions about callback_clear

What does the callback_clear tool do? +

callback_clear is a destructive tool on the Zebbern Kali MCP server. It is categorised as a Destructive tool in the Zebbern Kali MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on callback_clear? +

Register the Zebbern Kali MCP server in PolicyLayer and add a rule for callback_clear: 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 callback_clear? +

callback_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit callback_clear? +

Yes. Add a rate_limit block to the callback_clear 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 callback_clear completely? +

Set action: deny in the PolicyLayer policy for callback_clear. 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 callback_clear? +

callback_clear 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.

KEEP EXPLORING

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

This server

All 133 Zebbern Kali tools → Critical-risk tools on this server →

Across the catalogue

clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP →clear_spam_box on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →