Base Trading Agent

Snyk Agent Scan

Discover and scan agent components on your machine for prompt injections and vulnerabilities (including agents, MCP servers, skills).

> Note: We don't publish an npm package for Agent Scan. Install it via uvx or as a standalone binary.

> Note: CLI output is experimental and subject to change > > Agent Scan v0.5.x (planned for deprecation) > > The raw output of this CLI — including issue codes, field names, severity labels, and response structure — is experimental and may change without notice between releases. We do not recommend building production workflows that depend on specific CLI output fields or issue codes. > > Agent Scan v0.6 and later > > The raw output of this CLI — including risk indicator names, scores, field names, and response structure — is experimental and may change without notice between releases. We do not recommend building production workflows that depend on specific CLI output fields or risk names. > > If you are an enterprise customer using Snyk to manage agent security risk at scale, the CLI output may not reflect what is sent to and shown in the Evo platform. The underlying integration, discovery, and risk assessment that powers enterprise deployments is stable and supported — any changes will be communicated in line with standard Snyk product practices. Contact your account team for deployment guidance.

> NEW Read our technical report on the emerging threats of the agent skill eco-system published together with Agent Scan 0.4, which adds support for scanning agent skills.

Agent Scan v0.5.x output

> [!WARNING] > Agent Scan v0.5.x uses issue-code output. This CLI line is planned for deprecation.

Agent Scan v0.6 and later output

Agent Scan helps you discover all your installed agent components (harnesses, MCP servers, and skills) and scans them for common threats like prompt injections, sensitive data handling, or malware payloads hidden in natural language. Ignore analysis on skills by using --no-skills.

Security Warning

> ⚠️ IMPORTANT: Scanning MCP configurations can execute commands or make outbound network requests. > > To retrieve tool descriptions, Agent Scan starts stdio MCP servers by executing the commands in the config and connects to configured remote MCP server URLs with their configured headers. > > Recommendations: > - Run scans inside a sandbox (Docker container, VM, or disposable environment) when evaluating untrusted or third-party MCP configs > - Review the consent prompt carefully during interactive scans; it shows the command or remote URL for each server > - Use --dangerously-run-mcp-servers only in trusted environments where you've verified all MCP server commands and remote URLs > > Remote MCP requests refuse destinations resolving to link-local addresses or known cloud-metadata endpoints (169.254.0.0/16, fe80::/10, fd00:ec2::254, and 100.100.100.200). Loopback and private addresses remain allowed for local and internal MCP servers. HTTP redirects are not followed. DNS is validated before each request, but resolution again at connection time leaves a DNS-rebinding window. > > By default, Agent Scan requires explicit user consent (y/n) before contacting each discovered MCP server during foreground interactive runs. Background and push-key scans continue to inspect remote servers automatically for fleet coverage, but do not start stdio servers unless --dangerously-run-mcp-servers is set.