# download_file

Read/download a file from the Kali Linux container. Useful for retrieving scan results and output files.

Agent View of the PolicyLayer registry record for `download_file`. HTML page: https://policylayer.com/tools/hannes221-kali-mcp/download-file

## Facts

- Tool: `download_file`
- Server: Kali (`hannes221/kali-mcp`) — https://policylayer.com/tools/hannes221-kali-mcp.md
- Homepage: https://github.com/Hannes221/kali-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "download_file",
    "arguments": {}
  }
}
```

## Why download_file is rated Low

This tool retrieves files from the container without modifying, deleting, or executing anything. It is a simple read operation with no destructive or harmful side effects. The severity is low because unauthorized file access depends on what files exist and their sensitivity, but the tool itself performs only retrieval. Confidence is high due to the explicit 'Read/download' language in the description.

From the tool's own definition: "Tool description states 'Read/download a file' and is described as 'Useful for retrieving scan results and output files.' The verb 'download' and 'read' clearly indicate data retrieval with no side effects."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Kali:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "download_file": {}
  }
}
```

## Other tools on Kali (6)

- `container_stop` — Destructive — https://policylayer.com/tools/hannes221-kali-mcp/container-stop.md
- `container_start` — Execute — https://policylayer.com/tools/hannes221-kali-mcp/container-start.md
- `execute_command` — Execute — https://policylayer.com/tools/hannes221-kali-mcp/execute-command.md
- `container_status` — Read — https://policylayer.com/tools/hannes221-kali-mcp/container-status.md
- `list_files` — Read — https://policylayer.com/tools/hannes221-kali-mcp/list-files.md
- `upload_file` — Write — https://policylayer.com/tools/hannes221-kali-mcp/upload-file.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=hannes221-kali-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/hannes221-kali-mcp