Skip to main content
Quint’s policy engine evaluates every tool call against a set of YAML rules before the tool executes. If a rule matches, the SDK blocks the call and raises ToolBlockedError.

Default policy

The SDK ships with a built-in policy that blocks common dangerous patterns:

Custom policy

Pass a YAML file or dict to quint.init():

Rule structure

Matchers

Path expressions

The path field accesses the tool call context:

Examples

Block all file writes to /etc

Block network calls to internal APIs

Escalate (allow but flag) database mutations

Block pip install in production