Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent incident.io integration, but it gives an agent live authority to create, edit, close, and publicly update incidents without clear confirmation or safety guidance.
Install only if you trust the workspace and intend the agent to operate on real incident.io data. Use a least-privilege API key, prefer test or retrospective mode when practicing, and require human review before creating, closing, editing, or posting incident updates because these actions can notify responders or expose information.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use this auth pattern:
curl -s "https://api.incident.io/v2/..." \
-H "Authorization: Bearer $INCIDENTIO_API_KEY" \
-H "Content-Type: application/json"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use this auth pattern:
curl -s "https://api.incident.io/v2/..." \
-H "Authorization: Bearer $INCIDENTIO_API_KEY" \
-H "Content-Type: application/json"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use this auth pattern:
curl -s "https://api.incident.io/v2/..." \
-H "Authorization: Bearer $INCIDENTIO_API_KEY" \
-H "Content-Type: application/json"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use this auth pattern:
curl -s "https://api.incident.io/v2/..." \
-H "Authorization: Bearer $INCIDENTIO_API_KEY" \
-H "Content-Type: application/json"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use this auth pattern:
curl -s "https://api.incident.io/v2/..." \
-H "Authorization: Bearer $INCIDENTIO_API_KEY" \
-H "Content-Type: application/json"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use this auth pattern:
curl -s "https://api.incident.io/v2/..." \
-H "Authorization: Bearer $INCIDENTIO_API_KEY" \
-H "Content-Type: application/json"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use this auth pattern:
curl -s "https://api.incident.io/v2/..." \
-H "Authorization: Bearer $INCIDENTIO_API_KEY" \
-H "Content-Type: application/json"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
All requests use this auth pattern:
curl -s "https://api.incident.io/v2/..." \
-H "Authorization: Bearer $INCIDENTIO_API_KEY" \
-H "Content-Type: application/json"
The skill includes ready-to-run examples that create and modify live incidents but does not clearly warn users that these are write operations against a production API. This increases the risk of accidental incident creation, escalation, or closure when a user copies commands without realizing they will change real organizational state.
This finding points to the same create-incident example, which is a mutating authenticated call to an external API. In this context, the risk is accidental state change in a production incident-management system if run without clear warnings.
Required fields: idempotency_key, visibility. A severity_id is needed to open an active incident.
curl -s -X POST "https://api.incident.io/v2/incidents" \
-H "Authorization: Bearer $INCIDENTIO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
This finding points to the same create-incident example, which is a mutating authenticated call to an external API. In this context, the risk is accidental state change in a production incident-management system if run without clear warnings.
Required fields: idempotency_key, visibility. A severity_id is needed to open an active incident.
curl -s -X POST "https://api.incident.io/v2/incidents" \
-H "Authorization: Bearer $INCIDENTIO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
This is the same edit-incident example and involves a live authenticated write to an external service. It is risky because it can alter incident metadata and trigger notifications if executed against production data unintentionally.
Only provided fields are updated; omitted fields remain unchanged.
curl -s -X POST "https://api.incident.io/v2/incidents/INCIDENT_ID/actions/edit" \
-H "Authorization: Bearer $INCIDENTIO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
This is the same edit-incident example and involves a live authenticated write to an external service. It is risky because it can alter incident metadata and trigger notifications if executed against production data unintentionally.
Only provided fields are updated; omitted fields remain unchanged.
curl -s -X POST "https://api.incident.io/v2/incidents/INCIDENT_ID/actions/edit" \
-H "Authorization: Bearer $INCIDENTIO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
This is the close-incident edit call and performs a live external state change. Running it against the wrong incident or status could disrupt incident handling and produce inaccurate records.
Then update the incident:
curl -s -X POST "https://api.incident.io/v2/incidents/INCIDENT_ID/actions/edit" \
-H "Authorization: Bearer $INCIDENTIO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
This is the close-incident edit call and performs a live external state change. Running it against the wrong incident or status could disrupt incident handling and produce inaccurate records.
Then update the incident:
curl -s -X POST "https://api.incident.io/v2/incidents/INCIDENT_ID/actions/edit" \
-H "Authorization: Bearer $INCIDENTIO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
This is the same post-update example and represents a live authenticated write to the external incident service. The primary risk is accidental publication of sensitive or incorrect status information to incident stakeholders.
curl -s -X POST "https://api.incident.io/v2/incident_updates" \
-H "Authorization: Bearer $INCIDENTIO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
This is the same post-update example and represents a live authenticated write to the external incident service. The primary risk is accidental publication of sensitive or incorrect status information to incident stakeholders.
curl -s -X POST "https://api.incident.io/v2/incident_updates" \
-H "Authorization: Bearer $INCIDENTIO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
The skill tells users to export an API key and use it in shell commands but does not include guidance on protecting the credential from shell history, logs, screenshots, or accidental echoing. While the examples do not directly print the secret, missing handling guidance can still lead to credential exposure in operational use.