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

callback_status

A read tool on the Zebbern Kali MCP server.

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/callback-status.md

What callback_status does on Zebbern Kali MCP

AI agents call callback_status 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 callback_status is rated Low

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…

Questions about callback_status

What does the callback_status tool do? +

callback_status is a read tool on the Zebbern Kali MCP server. 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.

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

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