Security audit
Security checks for vulnerabilities and agentic risk
This read-focused skill also includes commands that can change or cancel a child's school arrangements without requiring confirmation.
Review before installing. For account checks, restrict requests to reads and necessary authentication calls. Separate attendance and pickup changes into an explicitly authorized workflow that verifies the child, date, and intended action. Confirm the API host through your school portal, protect account credentials, and inspect the missing live-check script before running it. The bundled write commands are documented examples, not automatic actions.
The linked request reference includes a live DELETE operation that cancels an arrival/dismissal change, despite this skill's read-oriented description. Using that recipe outside explicitly authorized write work could remove an intended student arrangement and affect school pickup coordination.
The skill advertises account reads but directs the agent to ready-to-run reference recipes that also include POST studentchange. This scope mismatch can lead an agent handling a read-only request to modify a child's attendance or dismissal arrangements; the supplied material does not establish malicious intent.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Ready-to-run requests
Shapes come from the SchoolPass Swagger spec and `docs/SCHOOLPASS-API.md`. Run
the live check (`node --env-file=.env scripts/live-check.mjs`) once to confirm
the auth-response fields on your account before trusting the `jq` recipes below.
## Helper — source this first
The reference supplies authenticated POST and DELETE recipes that create and cancel student changes, extending a read-only skill into live mutations. These are documented examples rather than automatically executed actions, but an agent following them can alter sensitive attendance and dismissal records without a write-specific authorization boundary.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# on disk, but keep this skill's state self-contained regardless).
SP_SESSION="${SCHOOLPASS_CURL_SESSION:-$HOME/.schoolpass-mcp/curl-token.json}"
# sp_curl <method> <path> [body-json] [-- extra-curl-args...]
# Adds the AppCode header, Authorization (if $SP_TOKEN set), and JSON accept.
sp_curl() {
local method="$1" path="$2" body="${3:-}"
The ready-to-run examples contain concrete student, date, and change-series identifiers without a mandatory target-validation or confirmation step. Although the section labels these operations as writes, copying or executing the examples against a live account could unintentionally submit an absence or cancel a change if the identifiers are valid and authorized.