jira-issue

Pass

Audited by Gen Agent Trust Hub on Nov 16, 2026

Risk Level: SAFEINDIRECT_PROMPT_INJECTIONCOMMAND_EXECUTIONCREDENTIALS_UNSAFE
Full Analysis
  • [INDIRECT_PROMPT_INJECTION]: The skill ingests untrusted data from Jira issue fields (summaries, descriptions, comments) which could contain malicious instructions.
  • Ingestion points: issue data is fetched in SKILL.md (Step 3.1) and via API calls defined in references/JIRA_API.md.
  • Boundary markers: The skill contains explicit instructions to ignore instructions embedded in ticket content and treat it as untrusted data.
  • Capability inventory: The skill uses bash to execute curl commands for network operations and view to read configuration files.
  • Sanitization: instructions require any detected malicious content to be quoted back to the user while the agent is forbidden from executing it.
  • [COMMAND_EXECUTION]: The skill uses the bash tool to facilitate interaction with the Jira REST API.
  • Evidence: SKILL.md and references/JIRA_API.md define curl workflows for issue creation and updates.
  • Mitigation: The skill employs secure credential management by passing tokens to curl using the -K flag via process substitution, preventing sensitive information from appearing in process listings.
  • [CREDENTIALS_UNSAFE]: The skill utilizes a local .env file to store and retrieve Jira API credentials when an MCP server is unavailable.
  • Evidence: README.md and references/JIRA_API.md document the use of JIRA_API_TOKEN and JIRA_USERNAME.
  • Refinement: This configuration is consistent with standard secret management practices and is supported by guardrails that strictly prohibit the agent from leaking or logging these credentials.
Audit Metadata
Risk Level
SAFE
Analyzed
Nov 16, 2026, 01:00 PM