Low Risk

callback_status

callback_status

How to control callback_status ↓

AI agents call callback_status 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.

Low Risk

The name suggests a status-check operation typical of Read operations. However, in a Kali Linux penetration testing context with sibling tools like 'ad_psexec' and 'ad_wmiexec' that establish remote access callbacks, 'callback_status' most likely monitors callback listeners or reverse connections. This would be a query operation with no side effects.

From the tool's definition Tool name 'callback_status' with no description provided. Based on naming convention and sibling tools (which include reconnaissance and exploitation functions), this appears to query the status of callback mechanisms, likely reading state without modifying…

Documented attack patterns abuse exactly the kind of access callback_status 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_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "callback_status": {}
  }
}

callback_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Zebbern Kali MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the callback_status tool do? +

callback_status. 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 callback_status? +

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

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

Can I rate-limit callback_status? +

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

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

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

Enforce policy on every Zebbern Kali MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.