Snyk
Read Snyk issues, projects, targets and SBOMs, and audit an organization's security posture.
About
Snyk ships in the w6w first-party pack. It declares 20 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.snyk- Version
- 0.1.1
- Author
- w6w
- Licence
- MIT
- Categories
- Security & Identity · Developer Tools
Overview
Snyk reads issues, projects, targets and SBOMs, and audits an organization’s security posture, across every org a token can reach. Issues can be listed and read individually, filtered by their effective severity — the one that already accounts for an organization’s own policies and ignores, which is what a triage workflow should actually act on — and the same query can run across every organization in a group rather than one at a time.
Projects, the repositories they came from, and the collections they’re grouped into can all be listed and read, a project’s tags and lifecycle can be updated, and a project or target can be removed along with its history. Software bills of materials can be generated per project in either CycloneDX or SPDX format, and known vulnerabilities can be looked up for a single package or a whole dependency list at once by package URL.
Every request is pinned to a specific, fixed API version rather than tracking Snyk’s latest, so response shapes stay stable under a running workflow even as Snyk ships new versions elsewhere. Minting or rotating credentials, on-premise broker connections, and Snyk Learn content are left out, since none of them fit a workflow step the way reading security data does.
Build with Snyk
Three routes to the same 20 actions. The Workflow tab is generated from Snyk's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Get issues for many packages
package-issues-list List known issues for a set of package versions, by purl.
Update a project
project-update Change a project's tags, environment, lifecycle or business criticality.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Snyk's real ids.
{
"manifestVersion": "2",
"name": "snyk-example",
"steps": [
{
"id": "collection-project-list",
"uses": {
"app": "io.w6w.snyk",
"action": "collection-project-list",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"collectionId": "<collectionId>"
}
}
]
}Here are some of the things you can do
-
List a collection's projects
readcollection-project-list -
List audit logs
readaudit-log-list -
List collections
readcollection-list -
List groups
readgroup-list -
Get an issue
readissue-get
+15 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Snyk, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Snyk. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "collection-project-list",
payload: {
// orgId: "<value>",
collectionId: "<value>",
// returnAll: "<value>",
// limit: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action collection-project-list --payload '{"collectionId":"<value>"}'Give an AI agent Snyk — without giving it Snyk's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.snyk#collection-project-list",
"input": {
"collectionId": "<collectionId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Snyk connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Snyk's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Snyk itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Snyk declares its own checks, so its health is a property of the app rather than something the host guesses at.
Snyk platform status
Atlassian Statuspage rollup for status.snyk.io, with per-region component detail. Unauthenticated and unsigned.
Pinned API version still served
Reads Snyk's `snyk-version-served`, `snyk-version-lifecycle-stage` and `sunset` headers to catch a pinned date going stale before calls start failing.