ClawHub
Back to skill

Security audit

Maverick Jira Mcp

Security checks for vulnerabilities and agentic risk

Overview

This skill coherently connects an agent to Jira through Atlassian Rovo MCP, with disclosed OAuth token storage and disclosed Jira write capability.

Install this only for an Atlassian account whose Jira permissions you are comfortable letting the agent use. Review the live tool catalog before use, avoid passing unrelated sensitive data into Jira tool arguments, and revoke the OAuth grant in Atlassian when you no longer need the skill.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (3)

Tp4

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

The declared description says this skill is for Jira issue tracking and workflow updates through Atlassian Rovo's MCP server, acting as a thin pass-through to that server's advertised tools. The supplied code does not interact with Jira, Atlassian Rovo, issue data, workflow state, or any remote Jira/MCP tool catalog. Instead, it is infrastructure/setup code for OAuth credential initialization: it derives environment variable names, extracts OAuth-related configuration from a local JSON config, constructs a token payload, and stores it in an mcporter vault. This is a materially different primary purpose and introduces undeclared sensitive credential-handling capabilities.

Content

No source excerpt is available for this finding.

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

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

md
- `MAVERICK_JIRA_MCP_EXPIRES_IN`
- `MAVERICK_JIRA_MCP_REFRESH_TOKEN_EXPIRES_AT`

These expiry fields are vault metadata, not tool arguments. They let mcporter make better pre-request refresh decisions for the access token and preserve refresh-token expiry information when the upstream OAuth response includes it.

**Setup-time prerequisites.** Setup needs `bash`, `jq`, and `mcporter` (>= v0.11.0) on `PATH`. These are gated by the install caller, not by `requires.bins` in this file, which gates agent-runtime eligibility. If setup fails, verify those binaries are present and current before retrying.

Unrestricted Tool Access

Medium
Category
Excessive Agency
Confidence
82% confidence
Finding

The skill instructs the agent to enumerate a live remote tool catalog and then 'call any tool from the catalog,' effectively delegating capability scope to whatever the remote Atlassian MCP server advertises at runtime. This creates a dynamic trust boundary: if the server exposes unexpected write, admin, or destructive tools, the agent may treat them as in-scope without local allowlisting, increasing the risk of unintended Jira mutations or abuse of the connected account.

Content

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

The output includes the server's Instructions: field (read it) and a JSON Schema for every tool's parameters. Treat this as the authoritative reference for the rest of the session.

Step 2 — Call any tool from the catalog using the form maverick-jira-mcp.<tool>:

sh
mcporter --config {baseDir}/mcporter.json call maverick-jira-mcp.<tool> <arg>=<value> ...

Static analysis

Detected: suspicious.exposed_secret_literal

File appears to expose a hardcoded API secret or token.

Critical
Code
suspicious.exposed_secret_literal
Location
scripts/init-mcporter-oauth.sh:77