awslabs.aws-for-sap-management-mcp-server@0.1.2
VERIFIED· install onlyPublisher claims: "An AWS Labs Model Context Protocol (MCP) server for AWS Systems Manager for SAP" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 8 of 12 bundled scripts run with no arguments (the rest were not run: per-bundle cap), with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso amazon.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it under the guard. Bundled scripts ran with no arguments; no agent task scenario for this bundle. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 0.1.1
vet-skills diff awslabs.aws-for-sap-management-mcp-server 0.1.1 0.1.2This version reaches for something 0.1.1 did not: 1 new host (amazon.com). Compared from the two recorded runs, not from source.
- New hosts
- amazon.com
0.1.1 was not run in the sandbox (static only); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-17 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 1 s · 2 scenarios · 0 deviationsStatic findings
chmod o+x /rootFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.No other findings across 14,002 lines in 35 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Not checked against OSV yet; the weekly check has not reached this version.