Security audit

Publish Jira

Security checks for vulnerabilities and agentic risk

Overview

This is a straightforward Jira API reference skill, but it can read and change Jira data using the user's Atlassian token.

Install only if you want an agent to use your Jira Cloud API token for Jira work. Prefer a token/account with the minimum Jira permissions needed, and review any delete, bulk create, notification, sprint, board, or issue-changing action before it is executed.

A.I.G

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

SkillSpector

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (5)

Tool Parameter Abuse

High

Category: Tool Misuse
Content: #### Delete Board ``` DELETE /rest/agile/1.0/board/{boardId} ``` #### Get Board Configuration
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).

Tool Parameter Abuse

High

Category: Tool Misuse
Content: #### Delete Sprint ``` DELETE /rest/agile/1.0/sprint/{sprintId} ``` #### Get Issues for Sprint
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).

Tool Parameter Abuse

High

Category: Tool Misuse
Content: #### Delete Issue ``` DELETE /rest/api/3/issue/{issueIdOrKey}?deleteSubtasks=true ``` #### Assign Issue
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).

Missing User Warnings

Medium

Confidence: 87% confidence
Finding: The skill instructs users to supply JIRA_EMAIL and JIRA_API_TOKEN and use them for Basic Auth over API requests, but it does not warn that credentials will be used to access and transmit account and workspace data. For markdown files, behaviors affecting privacy or sensitive account access should be disclosed to users.

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: This markdown file documents destructive and state-changing actions such as deleting boards, deleting sprints, and later deleting issues, but it does not include any cautionary note that these actions may permanently alter or remove project data. Under the markdown-specific warning criterion, skills should disclose behaviors that could affect user data or system integrity.

Static analysis

No suspicious patterns detected.