Cybersec Toolkit

by 26zl

Overview Schema Source Related Servers Discussions Admin

Python

Local

manage_remote_hosts

Add, list, test, or remove SSH hosts that run security tools on remote Linux machines over SSH.

Instructions

Add, list, test, or remove the SSH hosts that run_tool can target remotely.

Manages the remote-host registry that lets run_tool (and check_installed) run a tool on a remote Kali/Linux box over SSH instead of locally, so the tool only has to be installed on the remote. The action selects the operation: "list" shows every configured host; "add" registers or updates a host (needs name and hostname, plus optional user, port, ssh_key, and a tool_allowlist that restricts which tools may run there); "remove" deletes a host by name; "test" opens an SSH connection to confirm the host is reachable.

Connections use StrictHostKeyChecking=accept-new, so the key presented on the first connection is pinned in ~/.ssh/known_hosts and any later change is rejected. Verify that first fingerprint out-of-band for a host you do not control, or add the key to known_hosts before "test".

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No	Host name (required for add/remove/test).
`port`	No	SSH port (default 22).
`user`	No	SSH username (default "kali").	kali
`action`	Yes	Operation to perform: "list", "add", "remove", or "test".
`ssh_key`	No	Path to SSH private key (e.g. "~/.ssh/id_kali").
`hostname`	No	IP address or hostname of the remote machine (required for add).
`description`	No	Human-readable description of the host.
`tool_allowlist`	No	Comma-separated list of allowed tool names (e.g. "nmap,gobuster,sqlmap"). None means all tools allowed.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.2.1Sep 10, 2026

changedInput schema / properties / action / description

Previous value: -"One of \"list\", \"add\", \"remove\", \"test\"."New value: +"Operation to perform: \"list\", \"add\", \"remove\", or \"test\"."

addedInput schema / properties / action / enum

Added value: +[
+  "list",
+  "add",
+  "remove",
+  "test"
+]

First observedv1.2.0Sep 9, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It thoroughly describes the SSH connection behavior: using StrictHostKeyChecking=accept-new, pinning the first key, and rejecting subsequent changes. It also warns about verifying fingerprints out-of-band, which is critical safety information for an agent to understand the tool's security implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and appropriately sized. It opens with a clear summary of the tool's function, then breaks down each action in a logical flow, and ends with important security details. No sentence is wasted; each contributes to either clarifying functionality or providing necessary warnings.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (8 parameters, 4 actions, security implications) and rich input schema, the description covers all essential aspects for correct usage. It explains the relationship with sibling tools, parameter requirements per action, and safety concerns. The output schema is provided, so return value details are not needed. The description is comprehensive enough for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While schema description coverage is 100%, the description adds significant semantic value beyond the schema. It explains the role of name and hostname as required for specific actions, clarifies that tool_allowlist restricts which tools can run, and implies how parameters like port and user have defaults. Although the schema already documents each parameter, the description provides usage context that helps an agent choose and set parameters appropriately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: managing the remote-host registry that enables run_tool and check_installed to operate over SSH. It uses a specific verb ('Add, list, test, or remove') and resource ('SSH hosts'), and differentiates itself from sibling tools by explaining its role in supporting remote execution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use guidance by detailing each action ('list', 'add', 'remove', 'test') and their required parameters ('add' needs name and hostname; 'test' confirms connectivity). It also covers edge cases like tool_allowlist restrictions and provides clear context for when to use this tool vs. alternatives, such as run_tool for executing tools remotely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server