Pagerduty

Security checks across malware telemetry and agentic risk

Overview

This PagerDuty skill is a coherent integration, but it gives an agent broad power to change or delete live PagerDuty resources without clear confirmation safeguards.

Install only if you intend to let an agent operate PagerDuty through Membrane. Use a least-privilege PagerDuty/Membrane connection where possible, and require the agent to show the exact target resource and get explicit approval before any create, update, delete, resolve, snooze, reassign, or non-GET proxy request.

SkillSpector

By NVIDIA

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (2)

Missing User Warnings

Medium

Confidence: 95% confidence
Finding: The skill explicitly exposes destructive actions such as delete-service and update/create operations without any warning, approval requirement, or confirmation guidance. In an agent setting, that increases the chance that a vague or misinterpreted user request results in irreversible changes to live PagerDuty configuration or incident state.

Missing User Warnings

Medium

Confidence: 98% confidence
Finding: The proxy request section enables arbitrary authenticated API calls and documents mutation-capable HTTP methods including POST, PUT, PATCH, and DELETE, but provides no warning about live-data modification risk. This materially increases the blast radius because an agent can bypass safer pre-built actions and directly invoke powerful PagerDuty endpoints.

VirusTotal

63/63 vendors flagged this skill as clean.

View on VirusTotal