@ifasn/mmd-doc-mcp@1.0.3
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package automatically collects and stores cloud instance identifiers at runtime, creating a real but bounded privacy concern. The inspected source does not establish credential collection or external disclosure, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The package exposes index.js as its executable entrypoint and describes instance field mapping diagnostics.
- On startup, the program automatically queries the link-local metadata service for hostname, zone, instance, and account identifiers, then writes successful responses to output/meta_field_dump.txt.
- The metadata collection runs through configSync when the program starts.
- The inspected network request is a GET to the metadata service; no onward transfer of the collected values was identified.
- The reported runtime operations are ordinary Markdown table formatting.
- The inspected source shows local storage of metadata responses but no transmission of those responses to another endpoint.
Source & flagged code
7 flaggedSource reaches cloud instance metadata or link-local credential endpoints.
index.jsView on unpkg · L10On startup, the program automatically queries the link-local metadata service for hostname, zone, instance, and account identifiers, then writes successful responses to output/meta_field_dump.txt.
index.jsView on unpkg · L22Findings
Affected versions and remediation
This report applies to @ifasn/mmd-doc-mcp@1.0.3.
See all versions of @ifasn/mmd-doc-mcp for other recorded verdicts.
- Review the evidence and your use of @ifasn/mmd-doc-mcp@1.0.3 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.