Back to skill

Security audit

jobber-mcp

Security checks for vulnerabilities and agentic risk

Overview

The invoice-reading workflow is legitimate, but its persistent browser access is broader than the claimed read-only permission.

Review the browser grant before installing: treat it as persistent authenticated access to the approved domain, not an enforced read-only permission. Prefer a GET-only, narrowly scoped configuration if available, and revoke pairing when finished. Keep hub URLs private; stream HTML to the parser or use private temporary files and delete them afterward. The bundled files were fully reviewed, but the installed CLI and extension remain outside this artifact audit.

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
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (9)

Anti-Refusal Statement

High
Category
Anti-Refusal
Confidence
80% confidence
Finding

Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.

Content

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

md
looks like "you have no invoices" rather than like a bug.

The parser warns on stderr whenever it returns an empty list, for exactly this
reason. An empty result with no warning means the page genuinely had none.

## Exit codes

Skill declares no tool scope ('permissions' or 'allowed-tools') but code capabilities were detected: network.

Medium
Category
MCP Least Privilege
Confidence
70% confidence
Finding

Without declared permissions the skill's intent is opaque and cannot be validated.

Content

No source excerpt is available for this finding.

The troubleshooting workflow saves private invoice-page content to a fixed local file without warning about persistence or overwriting an existing file.

Medium
Category
Output Handling
Confidence
92% confidence
Finding

The troubleshooting command persists private invoice-page HTML to a predictable file using ordinary shell redirection, which truncates an existing file and creates new files with permissions determined by the user's umask. In a shared or synchronized working directory, this can expose customer information and potentially credential-bearing hub links; the recipe provides no cleanup or persistence warning.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · references/why-not-the-api.md (reported line 29)May include surrounding context.

sh
# unauthenticated: the field is hidden, not rejected
curl -s -X POST https://api.getjobber.com/api/graphql \
  -H 'Content-Type: application/json' \
  -H 'X-JOBBER-GRAPHQL-VERSION: 2025-04-16' \
  -d '{"query":"{ account { id name } }"}'

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · references/why-not-the-api.md (reported line 29)May include surrounding context.

sh
# unauthenticated: the field is hidden, not rejected
curl -s -X POST https://api.getjobber.com/api/graphql \
  -H 'Content-Type: application/json' \
  -H 'X-JOBBER-GRAPHQL-VERSION: 2025-04-16' \
  -d '{"query":"{ account { id name } }"}'

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · references/why-not-the-api.md (reported line 37)May include surrounding context.

md
#     unauthenticated"  (HTTP 200)

# bogus bearer: the token is checked, so the transport is fine
curl -s -X POST https://api.getjobber.com/api/graphql \
  -H 'Authorization: Bearer nope' ... 
# -> {"message":"Token not recognized"}  (HTTP 401)

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · references/why-not-the-api.md (reported line 42)May include surrounding context.

-> {"message":"Token not recognized"} (HTTP 401)

the OAuth token endpoint exists and validates client credentials

curl -s -X POST https://api.getjobber.com/api/oauth/token
-d 'grant_type=authorization_code&client_id=x&client_secret=y&code=z'

-> "The provided client id and secret do not match an existing application"

text

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · references/why-not-the-api.md (reported line 78)May include surrounding context.

md
Then the Developer API is the right answer and this skill is not: register an
app at `developer.getjobber.com`, take the `authorization_code` grant against
`https://api.getjobber.com/api/oauth/authorize`, and send
`X-JOBBER-GRAPHQL-VERSION` with every request. That is a different integration
with a different archetype — a bearer/direct-API client, no browser bridge.

The detail-page recipe saves invoice HTML locally and can overwrite an existing file without warning.

Low
Category
Output Handling
Confidence
92% confidence
Finding

The detail-page recipe writes sensitive invoice HTML to a fixed filename without restricting permissions or explaining retention. This can expose billing information through shared directories, synchronization or accidental commits, and it silently truncates any existing invoice.html.

Content

No source excerpt is available for this finding.