Propose a patch

Evidence

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

diff --git a/Dockerfile b/Dockerfile
--- a/Dockerfile
+++ b/Dockerfile
@@ -40,1 +40,0 @@
-#   docker run -v ~/.kube/config:/kube/config:ro \
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -127,1 +127,0 @@
-<summary><b>VS Code</b> (Copilot Chat) - <code>.vscode/mcp.json</code> in your workspace</summary> ```json { "servers": { "ocm-fleet": { "type": "stdio", "comma
@@ -347,1 +346,0 @@
-<summary><b>observability</b> - why a cluster is unhealthy</summary> - **`get_cluster_health`** *(read)* - hub conditions, unhealthy pods, degraded deployments.

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.6.0. 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: ocm-mcp-server: References a credential file in the home directory (KillerSkills verdict caution 66)

## 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 66/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/ocm-mcp-server/0.6.0

## Findings with a location
- `Dockerfile:40` · References a credential file in the home directory — Dockerfile:40 · References a credential file in the home directory
- `README.md:127` · Collapsed <details> block carrying instructions — README.md:127 · Collapsed <details> block carrying instructions
- `README.md:347` · Collapsed <details> block carrying instructions — README.md:347 · Collapsed <details> block carrying instructions

## 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._