Propose a patch

Evidence

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

diff --git a/src/servicenow_mcp/browser/login.py b/src/servicenow_mcp/browser/login.py
--- a/src/servicenow_mcp/browser/login.py
+++ b/src/servicenow_mcp/browser/login.py
@@ -516,1 +516,0 @@
-not, and the user can always type the password themselves. Every outcome is
diff --git a/src/servicenow_mcp/server.py b/src/servicenow_mcp/server.py
--- a/src/servicenow_mcp/server.py
+++ b/src/servicenow_mcp/server.py
@@ -449,1 +449,0 @@
-# This used to add "CLAUDE.md asks authors to keep descriptions ≤80

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.25.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: mfa-servicenow-mcp: Prompting user to enter sensitive credentials (KillerSkills verdict caution 65)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.7) and scored it **CAUTION 65/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/mfa-servicenow-mcp/1.25.17

## Findings with a location
- `src/servicenow_mcp/browser/login.py:516` · Prompting user to enter sensitive credentials — src/servicenow_mcp/browser/login.py:516 · Prompting user to enter sensitive credentials — social engineering
- `src/servicenow_mcp/server.py:449` · Instructs the agent to modify its persistent memory or instruction files — src/servicenow_mcp/server.py:449 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file · informational: not an instruction file

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