Propose a patch

A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 64 · Caution

Evidence

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

Diff · removes 6 caught lines

Download .patch

diff --git a/src/mcpbr/providers.py b/src/mcpbr/providers.py
--- a/src/mcpbr/providers.py
+++ b/src/mcpbr/providers.py
@@ -99,1 +99,0 @@
-"or pass api_key parameter."
@@ -192,1 +191,0 @@
-"or pass api_key parameter."
@@ -267,1 +265,0 @@
-"or pass api_key parameter."
@@ -424,1 +421,0 @@
-"or pass api_key parameter."
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -196,1 +196,0 @@
-<summary>Prerequisites</summary> - Python 3.11+ - Docker (running) - `ANTHROPIC_API_KEY` environment variable - Claude Code CLI (`claude`) installed - Network a
@@ -837,1 +836,0 @@
-<summary>Options and examples</summary> | Option | Short | Description | |--------|-------|-------------| | `--dry-run` | | Show containers that would be remove

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.14.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: mcpbr: Credential pass-through configuration (KillerSkills verdict caution 64)

## 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 64/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/mcpbr/0.14.0

## Findings with a location
- `src/mcpbr/providers.py:267` · Credential pass-through configuration — src/mcpbr/providers.py:267 · Credential pass-through configuration — agent relays sensitive credentials
- `src/mcpbr/providers.py:424` · Credential pass-through configuration — src/mcpbr/providers.py:424 · Credential pass-through configuration — agent relays sensitive credentials
- `src/mcpbr/providers.py:99` · Credential pass-through configuration — src/mcpbr/providers.py:99 · Credential pass-through configuration — agent relays sensitive credentials
- `src/mcpbr/providers.py:192` · Credential pass-through configuration — src/mcpbr/providers.py:192 · Credential pass-through configuration — agent relays sensitive credentials
- `README.md:837` · Collapsed <details> block carrying instructions — README.md:837 · Collapsed <details> block carrying instructions
- `README.md:196` · Collapsed <details> block carrying instructions — README.md:196 · Collapsed <details> block carrying instructions

## Proposed change
The attached patch removes the 6 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._

Open the issue on GitHub (greynewell/mcpbr)Fork to open a PR

# or from a terminal, under your own account:
gh repo fork greynewell/mcpbr --clone && cd mcpbr
curl -s https://killerskills.ai/skills/pypi/mcpbr/0.14.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.14.0 && git commit -am "mcpbr: Credential pass-through configuration"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/mcpbr/0.14.0/patch.md)

We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.