Propose a patch

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

diff --git a/kubev2v/kubevirt_server.py b/kubev2v/kubevirt_server.py
--- a/kubev2v/kubevirt_server.py
+++ b/kubev2v/kubevirt_server.py
@@ -519,1 +519,0 @@
-"ssh_key": "ssh-rsa AAAA...",  # SSH public key (from ~/.ssh/id_rsa.pub)
@@ -530,1 +529,0 @@
-2. Use public key content in ssh_key field: cat ~/.ssh/id_rsa.pub
@@ -532,1 +530,0 @@
-4. Create Kubernetes secret for key storage: kubectl create secret generic vm-keys --from-file=authorized_keys=~/.ssh/id_rsa.pub

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.17. If the behavior is intended, declare it (host under permissions.network, a line in the README) instead of removing it; the next crawl scores declarations.

Issue / PR body

Title: mtv-mcp: Reads credential paths from the home directory (KillerSkills verdict caution 68)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 68/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/mtv-mcp/1.0.17

## Findings with a location
- `kubev2v/kubevirt_server.py:530` · Reads credential paths from the home directory — kubev2v/kubevirt_server.py:530 · Reads credential paths from the home directory
- `kubev2v/kubevirt_server.py:519` · References a credential file in the home directory — kubev2v/kubevirt_server.py:519 · References a credential file in the home directory
- `kubev2v/kubevirt_server.py:532` · References a credential file in the home directory — kubev2v/kubevirt_server.py:532 · References a credential file in the home directory
- `kubev2v/kubevirt_server.py:530` · References a credential file in the home directory — kubev2v/kubevirt_server.py:530 · References a credential file in the home directory

## Proposed change
The attached patch removes the 3 lines above. If the behavior is intended, the fix is to declare it instead: list the host under `permissions.network` (or the MCP manifest) and say in the README why the package needs it; the next crawl will re-score it with the declaration taken into account.

## How this will be verified
Nothing is "verified safe" by assertion. When a new version is published, KillerSkills re-runs it in the honeypot and the verdict page updates; you can trigger it early from the verdict page ("Re-scan after I publish a fix"). Reply here or at [email protected] if you believe the verdict is wrong; disputes are reviewed by a person and the outcome is published on the verdict page.

_Proposed through killerskills.ai/threats by a user of the package, under their own GitHub account. The evidence is public; the package was never modified by KillerSkills._