Security audit
Security checks for vulnerabilities and agentic risk
The examples can expose your login credentials and leave children's school records in inadequately protected temporary files.
Review and correct the shell examples before use: keep passwords out of process arguments, avoid retaining exported credentials, and use private temporary files with cleanup for authentication output and child records. Authorize the exact child, dates and dismissal changes, then verify the saved result. Keep health-audit and password operations outside routine dismissal tasks. Both bundled files were reviewed; live API behavior and the separately referenced MCP server were not tested.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
---
name: pickuppatrol-api
description: "Read and change your children's school dismissal plans on PickUp Patrol (app.pickuppatrol.net) from a shell with curl — students, weekly defaults, day-by-day changes, school cutoff times."
---
# PickUp Patrol from a shell
The password is passed as a jq --arg argument and then embedded in curl's -d argument, despite being collected with a hidden prompt. Local processes or monitoring systems with access to process arguments could capture the credentials, potentially enabling access to children's information and unauthorized dismissal-plan changes.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -sS -c jar -X POST "$PUP/Authenticate" -H 'Content-Type: application/json' \
-d '{"provider":"credentials","UserName":"…","Password":"…","RememberMe":true}'
The reference includes GetParentHealthScreenAudits and its ScreenDate argument, enabling retrieval of health-screening audit information. This is a separate, potentially sensitive data category with no stated role in reading or changing students' dismissal plans.
The write-DTO reference provides the method and request fields for changing the user's account password. Changing account credentials is distinct from authenticating to read or update dismissal plans and is not justified by the manifest's stated purpose.
The workflow stores complete student records in predictable shared temporary paths without setting restrictive permissions or cleaning them up. Depending on local permissions and filesystem protections, another local user could read sensitive child information or pre-create or modify these files; the edited record is subsequently submitted to an endpoint that changes dismissal defaults.