Low Risk

shell_connection_read

Read the output buffer of a reverse-shell connection.

How to control shell_connection_read ↓

What shell_connection_read does on Kali-Mcp-Toolkit

AI agents call shell_connection_read to retrieve information from Kali-Mcp-Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why shell_connection_read needs a policy

The tool retrieves buffered output from an existing reverse-shell connection. While it does not execute new commands or modify data, it accesses potentially sensitive output from a reverse shell (often used in penetration testing to capture command results, system information, or credentials).

From the tool's definition Tool name contains 'read' and description states 'Read the output buffer' — explicitly a retrieval operation with no modification or execution.

Documented attack patterns abuse exactly the kind of access shell_connection_read gives an agent:

How to control shell_connection_read

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 shell_connection_read:

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

shell_connection_read 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 Kali-Mcp-Toolkit — 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.

Related tools and policies

Go deeper

Questions about shell_connection_read

What does the shell_connection_read tool do? +

Read the output buffer of a reverse-shell connection. It is categorised as a Read tool in the Kali-Mcp-Toolkit MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on shell_connection_read? +

Register the Kali-Mcp-Toolkit MCP server in PolicyLayer and add a rule for shell_connection_read: 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.

What risk level is shell_connection_read? +

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

Can I rate-limit shell_connection_read? +

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

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

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

Enforce policy on every Kali-Mcp-Toolkit tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.