oc_chain_plan
Validates CVE capability chains deterministically: checks step requirements/provided tokens, reports missing capabilities and cycles, attaches nuclei/trivy evidence, and persists the chain.
Instructions
Validate a CVE capability chain deterministically. Each step supplies requires/provides capability tokens, a written basis, and an optional evidence source; the tool computes satisfaction closure, missing tokens, and cycles, attaches nuclei/trivy artifact observations, and persists the chain. It never invents CVE semantics: annotate only what the advisory or evidence supports.
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": {
"engagement_id": "<engagement_id>",
"steps": "<steps>",
"entry_capabilities": "<entry_capabilities>"
},
"name": "oc_chain_plan"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| steps | Yes | ||
| artifacts | No | ||
| chain_name | No | ||
| engagement_id | Yes | ||
| entry_capabilities | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||