← azure@r10

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. 72 · Caution

Evidence

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

Diff · removes 4 caught lines

Download .patch
diff --git a/servers/Azure.Mcp.Server/README.md b/servers/Azure.Mcp.Server/README.md
--- a/servers/Azure.Mcp.Server/README.md
+++ b/servers/Azure.Mcp.Server/README.md
@@ -301,1 +301,0 @@
-<summary>GitHub Copilot CLI setup instructions</summary> #### Add Azure MCP Server 1. In a Copilot CLI session, run `/mcp add` to open the MCP server configurat
@@ -750,1 +749,0 @@
-<summary>Additional instructions</summary> **When to use local vs global installation:** - **Local (recommended):** Install in the project directory for project
@@ -794,1 +792,0 @@
-<summary>Additional instructions</summary> **When to use uvx vs pipx vs pip:** - **uvx (recommended):** Run directly without installation. Best for MCP server u
@@ -814,1 +811,0 @@
-<summary>Docker instructions</summary> #### Create an env file with Azure credentials 1. Create a `.env` file with Azure credentials ([see EnvironmentCredential

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of r10. 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: azure: Collapsed <details> block carrying instructions (KillerSkills verdict caution 72)

## What the honeypot observed
KillerSkills ran **azure@r10** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.7) and scored it **CAUTION 72/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/docker/azure/r10

## Findings with a location
- `servers/Azure.Mcp.Server/README.md:301` · Collapsed <details> block carrying instructions — servers/Azure.Mcp.Server/README.md:301 · Collapsed <details> block carrying instructions
- `servers/Azure.Mcp.Server/README.md:814` · Collapsed <details> block carrying instructions — servers/Azure.Mcp.Server/README.md:814 · Collapsed <details> block carrying instructions
- `servers/Azure.Mcp.Server/README.md:794` · Collapsed <details> block carrying instructions — servers/Azure.Mcp.Server/README.md:794 · Collapsed <details> block carrying instructions
- `servers/Azure.Mcp.Server/README.md:750` · Collapsed <details> block carrying instructions — servers/Azure.Mcp.Server/README.md:750 · Collapsed <details> block carrying instructions

## Proposed change
The attached patch removes the 4 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 (microsoft/mcp)Fork to open a PR
# or from a terminal, under your own account:
gh repo fork microsoft/mcp --clone && cd mcp
curl -s https://killerskills.ai/skills/docker/azure/r10/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/r10 && git commit -am "azure: Collapsed <details> block carrying instructions"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/docker/azure/r10/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.