Zebbern Kali MCP

Overview Schema Source Related Servers Discussions Admin

target_download_file

Download file content from a target system through an active session using SSH or reverse shell. Optionally verify SHA256 checksum to ensure integrity.

Instructions

Download file content from a target via an active session.

Args: session_id: Active session ID remote_path: Path to file on the target method: Transfer method (ssh, reverse_shell) verify_checksum: Verify SHA256 checksum if provided by the server

Returns: File content encoded as base64

Input Schema

TableJSON Schema

Name	Required	Default
`method`	No	ssh
`session_id`	Yes
`remote_path`	Yes
`verify_checksum`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 12, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It mentions return format (base64) but omits error handling, permissions, or whether the operation is safe. Behavioral traits beyond semantics are minimally disclosed.

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

Conciseness4/5

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

Purpose is stated in the first line, followed by structured Args and Returns. No extraneous text. Could be slightly more structured, but overall concise and front-loaded.

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

Completeness3/5

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

Given no annotations and an output schema, the description provides reasonable coverage: parameter meanings and return type. However, it lacks prerequisites (active session), error conditions, and method selection guidance, leaving gaps for a download tool.

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?

Schema has 0% description coverage, but the description's Args section adds meaningful explanations for all 4 parameters (e.g., 'Path to file on the target', 'Transfer method (ssh, reverse_shell)'). This compensates well for the missing schema descriptions.

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

Purpose4/5

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

Description clearly states 'Download file content from a target via an active session' with specific verb and resource. However, it does not differentiate from sibling tools like ssh_session_download_content or reverse_shell_download_content, which have similar functionality.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives, prerequisites (active session existence), or method selection. The Args section implies parameters but lacks usage context.

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

Deploy Server