Add or replace an organization checker
set_checkerAdd an organization checker, or replace the one with the same name. A checker is the organization's own HTTPS endpoint that implements Valet's Checker API. Once saved, a release policy can run it as org:: set_policy with that checker. Valet calls the endpoint's describe operation before saving and saves nothing if the call fails.
Saving a checker agrees, for the organization, to send the release files the endpoint asks for (the source, the build, or both) to the URL, for every release that a policy naming the checker evaluates. Once fetched, the files are outside Valet's control. Confirm that with the user before you call this tool. The answer names the files the endpoint asked for; those become the approved files. An endpoint that later asks for more is unavailable until the checker is saved again.
A credential header (Authorization, Cookie, X-Api-Key, or a name holding token, secret, key, or auth) takes exactly one {{NAME}} reference to a secret env var of the organization, after at most a scheme word, such as {"Authorization": "Bearer {{SNYK_TOKEN}}"}; any other text in it is refused. Valet resolves the reference at each call. Other headers are stored and listed as written, and a value in one that looks like a credential, such as a provider key or a URL with a user name, is refused. Have the user set the variable first with valet env set SNYK_TOKEN=... --org <org>, so the value never passes through this conversation. A reference to a variable that is not a secret of the organization is refused. list_policies shows the organization's checkers. Requires connecting a Valet account. Requires the Admin role.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"checker": "<checker>",
"url": "<url>"
},
"name": "set_checker"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Where the organization's checker service listens, such as https://checks.example.com/snyk. Valet calls /v1/describe and the other Checker API paths under it, so give the base, not a full path. | |
| checker | Yes | What to call the checker, such as snyk, so a policy can name it: set_policy runs it as org:snyk, the prefix marking a checker the organization added. Saving under a name already in use replaces that checker. | |
| headers | No | The credential and any other headers the endpoint expects on Valet's calls, as header name to value, such as Authorization to Bearer {{SNYK_TOKEN}}, where SNYK_TOKEN is the organization's secret holding the token. | |
| org_name | No | The Valet organization that owns the checker. Omit to use the organization the account joined first. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| org | Yes | Name of the Valet organization the call acted in. | |
| url | Yes | The endpoint's base URL as saved. | |
| fields | Yes | The settings a policy can give this checker, as the endpoint's describe operation reports them. Empty when it takes none. | |
| inputs | Yes | The release files the endpoint asked for and this save approved: source, build, or both. Valet sends them to the URL for every release a policy naming this checker evaluates. Empty when it asked for none. | |
| checker | Yes | The checker's name as a policy spells it, such as org:snyk. Pass it to set_policy as checker. | |
| headers | Yes | Headers Valet sends on every call, by name. A credential header shows its {{NAME}} reference, never a value. Empty when there are none. | |
| description | Yes | What the checker does, as the endpoint's describe operation reports it. Empty when the endpoint declares none. | |
| display_name | Yes | The name a person reads, as the endpoint's describe operation reports it. Empty when the endpoint declares none. |