send_input
A execute tool on the Zebbern Kali MCP server.
This record as markdown: /tools/zebbern-zebbern-kali-mcp/send-input.md
What send_input does on Zebbern Kali MCP
AI agents invoke send_input 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.
Why send_input is rated High
Given the server context (Docker-based Kali Linux pentest toolkit with remote execution tools like psexec and wmiexec as siblings), 'send_input' almost certainly sends arbitrary input to a running shell or process within the container. This constitutes Execute-category behavior with critical severity, as it could drive any offensive operation.
From the tool's definition Tool is part of a Kali Linux penetration testing MCP server with sibling tools including ad_secretsdump, ad_psexec, ad_wmiexec, ad_password_spray — all offensive security tools.
Attacks that exploit this kind of access
The rule that runs send_input 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 send_input, this is the rule to start with:
send_input 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Zebbern Kali MCP, apply this rule, and every send_input call is checked against it from then on.
Questions about send_input
send_input is a execute tool on the Zebbern Kali MCP server. 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 send_input: 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.
send_input 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 send_input 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 send_input. 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.
send_input 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.
Across the catalogue