Back to skill

Security audit

Openapi Validator

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only OpenAPI review skill with no hidden execution, persistence, or data exfiltration behavior.

Installers should expect this skill to inspect local API specification files and produce audit recommendations. Review the target files before use if the workspace contains private API designs, but the artifact shows no hidden mutation, network transfer, or persistence behavior.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · SKILL.md (reported line 120)May include surrounding context.

md
### 🔴 Critical (2)
1. **4 endpoints without security** — POST /webhooks, GET /health,
   GET /api/internal/stats, DELETE /api/cache
   → Apply security scheme or explicitly mark as public

2. **Sensitive data in query param** — GET /api/users?api_key={key}

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The example invocations include generic phrases like "Improve my API specification" and "Audit API design for REST best practices," which could overlap with ordinary requests about API documentation or design rather than a deliberate request to run this specific skill. The file does not provide negative examples, activation boundaries, or contextual constraints to clarify when the skill should or should not activate.

Content

No source excerpt is available for this finding.