tools

Language reference / tools

Meaning and placement

→ permits

Allowed nika:/mcp: tool ids · globs ok.

Property	Declaration
Requirement	Optional in this object
Schema location	`/properties/permits/properties/tools`
type	”array”

In the same object: env · exec · fs · net Schema source (use the pointer above)

agent

Whitelist · DEFAULT-DENY (no tools if absent) · gitignore-style globs · ! negation.

Property	Declaration
Requirement	Optional in this object
Schema location	`/$defs/agent/properties/tools`
type	”array”

In the same object: max_tokens_total · max_turns · model · prompt · schema · skills · system · temperature Schema source (use the pointer above)

In a source template

Excerpt from templates/agent-loop.nika.yaml, source lines 50–59. This is a fragment, not a runnable workflow.

illustration

permits:                            # the blast radius · default-deny once present
  # Exactly what the body invokes: `nika:assert` (the confirm task) plus the
  # two the agent may call. No `fs:` — see the note on `tools:` below.
  tools: ["nika:assert", "nika:done", "nika:jq"]

tasks:
  plan:
    infer:
      prompt: "Break '${{ inputs.goal }}' into at most 4 concrete steps."   # SLOT
      # SLOT: the spend ceiling for the planning call. Size it for the SEAT,

Templates containing this field

Template	Source
`templates/agent-loop.nika.yaml`	Line 53
`templates/api-upload-and-create.nika.yaml`	Line 52
`templates/chain.nika.yaml`	Line 37
`templates/classify-and-route.nika.yaml`	Line 74
`templates/corpus-qa.nika.yaml`	Line 29
`templates/docker-report.nika.yaml`	Line 41
`templates/document-to-fields.nika.yaml`	Line 35
`templates/etl-state.nika.yaml`	Line 55
`templates/fanout.nika.yaml`	Line 71
`templates/gate-and-act.nika.yaml`	Line 33
`templates/human-gated-ship.nika.yaml`	Line 62
`templates/media-asset-pack.nika.yaml`	Line 40
`templates/website-brief.nika.yaml`	Line 42

These are literal key occurrences in the source files, not an execution or conformance claim. How to instantiate a template.

Contract and implementation

This page projects the named specification revision. Check released engine status and the validation workflow before running a file. An optional field is not evidence that every engine supports every value. Canonical identity: language:word:tools. Spec revision: c5ebbb7b862b. How documentation stays connected.

YAML

Language fields

CLI & errors

Data catalogs

Workspace

Documentation system

Tool contracts

Meaning and placement

→ permits

agent

In a source template

Templates containing this field

Contract and implementation

​Meaning and placement

​→ permits

​agent

​In a source template

​Templates containing this field

​Contract and implementation

Meaning and placement

→ permits

agent

In a source template

Templates containing this field

Contract and implementation