Execute a command in an existing terminal session.
AI agents invoke terminal_exec to trigger actions in Kali-Mcp-Toolkit. 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.
This tool executes arbitrary commands in a terminal session, which can trigger external operations, modify system state, or run malicious payloads depending on agent arguments. While not inherently destructive (deletion is separate), command execution in a penetration testing toolkit context poses critical risk: an AI agent could execute privilege escalation, data exfiltration, lateral movement, or system compromise.
From the tool's definition Tool name 'terminal_exec' and description 'Execute a command in an existing terminal session' explicitly indicate execution of arbitrary commands in a terminal context.
Documented attack patterns abuse exactly the kind of access terminal_exec gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali-Mcp-Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for terminal_exec:
{
"version": "1",
"default": "deny",
"tools": {
"terminal_exec": {
"limits": [
{
"counter": "terminal_exec_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}terminal_exec 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.
Execute a command in an existing terminal session. It is categorised as a Execute tool in the Kali-Mcp-Toolkit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali-Mcp-Toolkit MCP server in PolicyLayer and add a rule for terminal_exec: 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 Kali-Mcp-Toolkit. Nothing to install.
terminal_exec 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 terminal_exec 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 terminal_exec. 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.
terminal_exec is provided by the Kali-Mcp-Toolkit MCP server (trymonoly/kali-mcp-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kali-Mcp-Toolkit, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Kali-Mcp-Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.