You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`cycode_secret_scan`| Scan files for hardcoded secrets |
388
-
|`cycode_sca_scan`| Scan files for Software Composition Analysis (SCA) - vulnerabilities and license issues |
389
-
|`cycode_iac_scan`| Scan files for Infrastructure as Code (IaC) misconfigurations |
390
-
|`cycode_sast_scan`| Scan files for Static Application Security Testing (SAST) - code quality and security flaws |
387
+
|`cycode_secret_scan`| Scan for hardcoded secrets|
388
+
|`cycode_sca_scan`| Scan for Software Composition Analysis (SCA) - vulnerabilities and license issues|
389
+
|`cycode_iac_scan`| Scan for Infrastructure as Code (IaC) misconfigurations|
390
+
|`cycode_sast_scan`| Scan for Static Application Security Testing (SAST) - code quality and security flaws|
391
391
|`cycode_status`| Get Cycode CLI version, authentication status, and configuration information |
392
392
393
+
Each scan tool accepts two mutually exclusive input modes:
394
+
395
+
- **`paths`***(preferred)* — one or more file or directory paths that exist on disk. Directories are scanned recursively. The Cycode engine handles file discovery and filtering, just as `cycode scan -t <type> path ./src` does from the CLI.
396
+
- **`files`***(fallback)* — a dictionary mapping file paths to their full content as strings. Use this only when the files are not available on disk (e.g. in-memory edits not yet saved).
397
+
398
+
> [!TIP]
399
+
> Use `paths` whenever possible. Passing large files (like `package-lock.json`) as inline content can exceed token limits and slow down the AI client. With `paths`, the Cycode engine reads files directly from disk.
400
+
401
+
All scan tools return a JSON object that includes a `"summary"` field with a human-readable violation count (e.g. `"Cycode found 3 violations: 1 CRITICAL, 2 HIGH."`) in addition to the full `"detections"` array.
> The MCP server requires proper Cycode CLI authentication to function. Make sure you have authenticated using `cycode auth` or configured your credentials before starting the MCP server.
549
559
560
+
### Pre-authorizing Tools for Subagents (Claude Code)
561
+
562
+
When Claude Code delegates work to background subagents (e.g. to run scans in parallel), those subagents cannot display interactive permission prompts. If the Cycode tools have not been pre-approved, scans will fail silently in subagent contexts.
563
+
564
+
To pre-authorize the Cycode MCP tools so they work in all contexts including subagents, add them to the `allowedTools` list in your Claude Code settings (`~/.claude/settings.json`):
565
+
566
+
```json
567
+
{
568
+
"allowedTools": [
569
+
"mcp__cycode__cycode_secret_scan",
570
+
"mcp__cycode__cycode_sca_scan",
571
+
"mcp__cycode__cycode_iac_scan",
572
+
"mcp__cycode__cycode_sast_scan",
573
+
"mcp__cycode__cycode_status"
574
+
]
575
+
}
576
+
```
577
+
578
+
Once added, Claude Code will not prompt for approval when these tools are called, and they will work correctly inside subagents.
579
+
550
580
### Troubleshooting MCP
551
581
552
582
If you encounter issues with the MCP server, you can enable debug logging to get more detailed information about what's happening. There are two ways to enable debug logging:
0 commit comments